Sabitlenmiş Tweet
UF InfoSec
265 posts

UF InfoSec
@UFSIT
@UF Student InfoSec Team | Thursdays @ 6:00pm in CSE E231. CTF team Kernel Sanders Host of @swampctf
Gainesville, FL Katılım Nisan 2013
330 Takip Edilen269 Takipçiler
UF InfoSec retweetledi

As of today, UFSIT is a part of @EFF's EFA! We're happy to endorse their values:
EFF@EFF
We support digital freedom: free expression, security, privacy, creativity, and access to knowledge eff.org/EFA
English
UF InfoSec retweetledi
UF InfoSec retweetledi

And the winners are....
1st place: A Team with a Dream - @UCF
2nd place: Cyber Eagles - @tennesseetech
3rd place: Darth Gator - @UF
Congratulations to all!!!



English
UF InfoSec retweetledi

CISE Dept Chair and FICS faculty member @DrJuanGilbert was recently honored with the National Medal of Technology by President Joe Biden.
The National Medal of Technology and Innovation is the nation’s highest honor for technological achievement.
news.ufl.edu/2023/10/juan-g…

English
UF InfoSec retweetledi

BugBounter gets together with @UFSIT of University of Florida (@UF) to talk about bug bounty as a method to develop as a cybersecurity specialist & make money!
📅 October 25th, 2023, Wed.
⏰ 4:45 PM EST / 11:45 PM GMT+3
#bugbounter

English
UF InfoSec retweetledi


People still qrt like this to get hits?
mRr3b00t@UK_Daniel_Card
Peole still tweet like this to get hits? ;)
English

@DebugPrivilege (shoutout to nushell for trying to bring this to linux)
github.com/nushell/nushell
English

@DebugPrivilege Anything shell that is intuitive is 10/10 for me
The predictable naming schema and the way that everything is an object instead of just text makes things so nice
English

@trashh_dev @NetflixEng me when I see that Netflix doesn't have a cybersecurity internship out yet

English

summer interns 2024 @NetflixEng
get it while it’s hot
jobs.netflix.com/jobs/298350570
English

@0xTib3rius I personally like to adjust my CVSS based on ✨vibes ✨
Too high bc of exploitability? The vibes say otherwise
English

The curl / libcurl CVE being High severity but only affecting a specific (and likely rare) use-case needs some discussion.
There are multiple things to consider here:
CVSS scores are usually just base metrics, cover the worst case scenario, and don't take exploitability into consideration. That doesn't make CVSS entirely useless, but context is always needed. Incidentally, the original H1 report (hackerone.com/reports/2187833) had this marked as a Critical.
A developer may not be fully aware of the prevalence of certain configurations of their product. It is likely more responsible to err on the side of caution in these cases.
However, perhaps in this situation, and going forward, it might be a good idea for developers to add some context to their initial pre-patch announcements.
I saw this described as the "worst curl security flaw in a long time", which is true, if we're talking about severity (possible outcomes) alone. The issue is, severity isn't the only important thing here. It would have been nice to know an estimation of exploitability too.
The counterpoint to that I suppose is that perhaps those who do need to urgently patch their systems would have been less aware. It's a tricky situation.
What are your thoughts?
English














