UF InfoSec

265 posts

UF InfoSec banner
UF InfoSec

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
SwampCTF
SwampCTF@SwampCTF·
SwampCTF is in 25 hours!!!! Here is a👀sneak peak👀! Get your emulators ready for some old school fun! #SwampCTF #CTF
SwampCTF tweet media
English
0
2
6
398
UF InfoSec retweetledi
Collegiate Penetration Testing Competition
CONGRATULATIONS to our FINAL 15 TEAMS! Please monitor your emails over the next few days to find out information and key deadlines for finals preparations! To team who competed in our Regionals we are honored that you have chosen to compete with us! Next Stop: FINALS 🚊 🛩 🎉
Collegiate Penetration Testing Competition tweet mediaCollegiate Penetration Testing Competition tweet media
English
1
8
23
2.5K
UF InfoSec retweetledi
CyberForce® Program
CyberForce® Program@DOECyberForce·
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!!!
CyberForce® Program tweet mediaCyberForce® Program tweet mediaCyberForce® Program tweet media
English
0
1
6
376
UF InfoSec retweetledi
UF FICS
UF FICS@uf_fics·
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…
UF FICS tweet media
English
0
2
9
431
UF InfoSec retweetledi
Bugbounter
Bugbounter@bugbounterr·
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
Bugbounter tweet media
English
0
1
1
284
UF InfoSec retweetledi
Collegiate Penetration Testing Competition
Here are our winners from our first round of Regionals! To all of the competitors, we want to Congratulate each of you on a job well done! Thank you to our regional hosts at Tennessee Tech University, Augusta University, and Baldwin Wallace University!
Collegiate Penetration Testing Competition tweet mediaCollegiate Penetration Testing Competition tweet mediaCollegiate Penetration Testing Competition tweet media
English
2
12
28
3.7K
UF InfoSec
UF InfoSec@UFSIT·
Our Red Team is officially in Augusta for @globalcptc! Everyone wish them luck! 🟥🟥🟥🟥🟥🟥🟥
UF InfoSec tweet media
English
0
0
1
130
mRr3b00t
mRr3b00t@UK_Daniel_Card·
Peole still tweet like this to get hits? ;)
GIF
English
5
0
6
7.4K
UF InfoSec
UF InfoSec@UFSIT·
@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
1
0
0
20
UF InfoSec
UF InfoSec@UFSIT·
@0xTib3rius I personally like to adjust my CVSS based on ✨vibes ✨ Too high bc of exploitability? The vibes say otherwise
English
0
0
0
38
Tib3rius
Tib3rius@0xTib3rius·
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
8
18
122
42.3K
Stuart Larsen
Stuart Larsen@c0nrad_jr·
The most important YouTube creator milestone
Stuart Larsen tweet media
English
3
0
36
2K