Yebo Cao

Ever played a CTF on IRC? I published a detailed walkthrough for all the 22 challenges for IRCPuzzles 2024 competition. Check it out here: https://lnkd.in/gcyJNdBk It's quite lengthy and almost a book at this point, so please use the table of contents to find what interests you! #ircpuzzles #ctf #puzzle

13

I wrote about the various rule combinations I’ve been testing in this post to block known bad and reduce load on the firewall. ~~ Are Your pfSense Filters Really Working? ~~ Too many rules and logs (?) makes them randomly fail ~~ To spot this you need to be monitoring your logs. I have been testing various combinations of rules and noticed this issue in certain scenarios. https://lnkd.in/eknrE6zG

3

ATTN: New Cyentia Institute study. If you're responsible for managing or remediating security vulnerabilities, you'll want to read this one. #vulnerabilitymanagement #cybersecurity #infosec #vulnerabilities

44

2 Comments

#Hof #4nd Excited to share another successful vulnerability disclosure Monash University's web app. This header plays a crucial role in preventing Cross-Site Scripting (XSS) attacks by protecting client-side parsers from MIME type sniffing. Although marked as informational, addressing this issue strengthens web security practices! 💪 Grateful to be recognized in the Monash University Hall of Fame for this contribution. Bug Type : Data Disclosure 🐞💻⌨️ Hall of Fame: https://lnkd.in/gVW-dYrg #CyberSecurity #BugBounty #XSS #VulnerabilityDisclosure #WebSecurity #HallOfFame #EthicalHacking

43

22 Comments

🚀 New blog post alert! I've just published the latest write-up for HTB Sherlock's "Nuts" challenge. This DFIR task was all about analyzing a large volume of artifacts and uncovering a malicious package. Dive into the investigation process and see how I tackled each step, from identifying key commands to tracing back the threat actor. If you're into #CyberSecurity, #DigitalForensics, or #MalwareAnalysis, this is for you! Read the full post here: https://lnkd.in/dF_YRpwp #DFIR #HTB #Sherlock #CTF #Infosec

10

🚀 New Blog Post Alert! 🚀 I’ve just published a new blog post detailing the answers I found for the HTB Sherlock ProcNet challenge. Check out how I uncovered the solutions to the questions posed and learn more about C2 frameworks and related cybersecurity techniques. 🔗 https://lnkd.in/dyswsgKa #HTB #Sherlock #DFIR #CyberSecurity #RedTeam #BlueTeam

5

If you have Snowflake environments, we've released an open-source tool tailored to detect suspicious activities: https://lnkd.in/g7S4777j. Concerned about threat actors accessing your Snowflake environments? Wondering what they do before or after gaining access? Connect with me to discuss recent attacks, threat indicators, and proactive hunting and detection measures. Need guidance on utilizing YetiHunter, exploring use-cases, or queries? Message me; I'm here to support the community. Time is the fundamental threat, let's collaborate to enhance cloud and SaaS detection capabilities and minimize risks from threat actors, misconfigurations, and vulnerabilities.

24

CISA released three Industrial Control Systems (#ICS) advisories on September 17, 2024. These advisories provide timely information about current security issues, vulnerabilities, and exploits surrounding ICS. ICSA-24-261-01 Siemens SIMATIC S7-200 SMART Devices ICSA-24-261-02 Millbeck Communications Communications Proroute H685t-w ICSA-24-261-03 Yokogawa Industry Solutions Dual-redundant Platform for Computer (PC2CKM) CISA encourages users and administrators to review newly released ICS advisories for technical details and mitigations. #cybersecurity #situationalawareness

1

No LLM is secure! But there is hope in using Short Circuiting (https://lnkd.in/gh5eefB5) Problem 1: Current alignment techniques can be easily bypassed by adversaries. (https://lnkd.in/gypvde78) Problem 2: Adversarial robustness often comes at the cost of degraded performance, to the point the system becomes undeployable. (https://lnkd.in/ggS74BX4) Problem 3: Adversarial training offers no guarantees against unknown attacks. #LLM #GenerativeAI #Security

51

3 Comments

I've been receiving many questions about VulnCheck NVD++ our free community service, so I created a video to demonstrate how quickly you can sign up for a free account and download the National Institute of Standards and Technology (NIST) NVD. The VulnCheck community service includes API access and CPE enrichment as well. It only took me about 30 seconds on Airbnb WiFi to sign up and complete the download of the full NIST NVD. I'm gonna go blow some fireworks off now... Happy 4th of July! #cybersecurity #infosecurity #vulnerabilitymanagement #riskmanagement

32

2 Comments

For security researchers interested in starting with reverse engineering Windows drivers IOCTLs, I highly recommend checking out my PDF presentation from my H2HC 2023 talk. It's a comprehensive resource to help you get started! https://lnkd.in/dchEYnNg #exploit #afd #reversing #vulnerability #ioctl #ioring #windows

169

9 Comments

Debug Bar Exposes Sensitive Information Vuln-Info][common-01-02][Tentative-High] - https://example.com [Sign-Info][Tentative-High] - /home/kali/jaeles-signatures/common/phpdebug.yaml - PHP Debug bar  subfinder -d your-target-domain | httpx -silent | anew | xargs -I@ jaeles scan -L 4 -c 20 -s ~/jaeles-signatures/* -u @ -o your-target-domain_jaeles.txt Vulnerability Details: Title: PHP Debug Bar Exposing Sensitive Information Severity: Medium Vulnerability Summary: This vulnerability exposes a potential security hole that could result in the exposure of sensitive data through the PHP Debug Bar, a development tool frequently used to inspect and profile PHP applications. https://lnkd.in/eTJrH5vt .

2

Reflecting on the current state of National Institute of Standards and Technology (NIST) NVD processing, it's evident that while the industry remains committed to contributing to coordinated CVE disclosure through the CVE Program, the NVD has continued to have a shortfall in their ability to processing vulnerabilities and remediate their issues. To shed light on the contributions of CVE Numbering Authorities (CNAs) and the gaps in NVD processing, I've mapped the CVE's issued by each CNA to NVD's issued in 2024 with the current CVE Status. NIST's lack of communication and follow through has raised significant concerns within the security community regarding the future of NVD. It'll be interesting to observe how this situation unfolds from here. Jerry Gamblin Chris Hughes Jay Jacobs ☁️ Francesco ☁️ Cipollone Wade Baker, Ph.D. Stephen Shaffer Ben Edwards Catalin Cimpanu Josh Bressers Tom Lawrence ✅ Kevin Poireault #cybersecurity #infosecurity #riskmanagement #vulnerabilitymanagement

168

30 Comments

Mailing #pwned learn how LFI lead system Takeover and how easy to crack the password of the user. LFI Mitigation: Input Validation: This is the primary defense. Validate all user-supplied input to ensure it only contains expected characters and doesn't point to unauthorized files. Disable Directory Listing: Web servers often offer directory listings, which can reveal file paths and structures. Disable this feature to prevent attackers from guessing potential file locations. Use Safe Functions: Employ functions designed for file inclusion, such as include_once in PHP, which prevent loading arbitrary files. Avoid using functions like include or eval that can execute code based on user input. Strong Password Practices: Length is Key: Aim for passwords at least 12-15 characters long. The more characters, the harder it is to crack. Complexity is Crucial: Combine uppercase and lowercase letters, numbers, and symbols for maximum strength. Avoid Common Phrases: Don't use personal information, dictionary words, or easily guessable phrases. Uniqueness for Each Account: Don't reuse passwords across different platforms. A data breach on one site shouldn't compromise your others. Password Managers: Consider using a password manager to generate and store strong, unique passwords for all your accounts. #HTB #CTF #pentest #Vulnerabilities #Cybersec

13

1 Comment

Tired of getting your reports marked as N/A or informational or Duplicate ? I come across many bug hunters who are fairly new into BBH like myself and they find it very frustrating to get almost all of their reports marked as either N/A, Informational or Duplicate. So I decided to share some of my personal tips on how I approached and addressed this problem early on. 1) To avoid getting N/A , informational: Whenever you come across a bug or a quirk / unintended behavior always ask yourself the question "What can an actual attacker do with this" or "What can an attacker achieve using this bug". If you have an answer to that then that's your potential impact of the bug. 2) Dealing with Duplicates: Duplicates hurts the most because you know the bug is valid but you weren't the first one to submit it. There's only one solution to this and that is to "Escalate, Escalate and Escalate". Whenever you come across a bug make sure to always Escalate it to its maximum impact, this way you'd drastically reduce the amount of duplicates you get and because you escalated a bug means that it's going to have a higher impact which means more $$$. One of the tools that I use to get escalation suggestion and calculate cvss is "cvssadvisor.com" developed by @bebiksior on ( X, twitter) These were some of the things I learned Bi idhnillah that helped me overcome those problems. I hope this is going to be helpful to people that are new into BBH or have some what experience but still struggling with those problems 😃 #bugbounty #bugbountytips

1

How to Build and Run a CTF Organization: Expert Tips and Tricks Learn how to set up and run a Capture The Flag (CTF) organization with step-by-step instructions from a seasoned pro. Discover the secrets to creating engaging competitions that appeal to both technical and non-technical participants. Get ready to boost your cybersecurity skills! #CTF #Cybersecurity #HackingCompetition #CaptureTheFlag #EthicalHacking #CybersecurityTraining #CybersecuritySkills #CTFOrganization #CybersecurityTips #EngagingCompetitions

3

✨ Waiting for Bounty! ✨ I recently discovered a critical unauthorized access vulnerability on a well-known platform, where admin-level endpoints were left exposed. 🚨 These endpoints allowed for data manipulation, metadata extraction, and unauthorized access, potentially compromising the integrity and confidentiality of sensitive information. 💻 Methodology: JavaScript File Analysis: Identified deeply embedded and vulnerable directories through dynamic analysis. Endpoint Enumeration: Mapped publicly accessible and admin-level pages. Access Control Testing: Validated improper restrictions and manipulated parameters to confirm unauthorized access. 🔒 Impact: This vulnerability highlights how overlooked endpoints can lead to severe security risks, emphasizing the importance of thorough access control reviews and endpoint hardening. 👾 Bug hunting continues to be a rewarding and challenging journey! 💡 #CyberSecurity #BugBounty #InfoSec #EthicalHacking #WebSecurity

119

This week, the National Institute of Standards and Technology (NIST) National Vulnerability Database (NVD) is scheduled for maintenance. We've already noticed that the NVD stopped adding new vulnerabilities to its database as of yesterday, 3-days ahead of the scheduled maintenance window. 🤷‍♂️ 🤦‍♂️ The good news is that the VulnCheck NIST-NVD feed pulls source data directly from the CVE Program, which is free. So, even during NIST NVD's maintenance, you'll still have access to the complete list of CVE records and NIST enrichments in a single source. As for the maintenance itself, this is purely speculative, but I suspect this work might be related to expanding the ingestion of Cybersecurity and Infrastructure Security Agency VulnEnrichment data. If that's the case, it could help reduce a significant portion of the NVD backlog. I suspect this could create a flood of new visibility for practitioners as the information proliferates across their VM tools. On another note, it would be much nicer if NIST were more transparent about what they’re working on, rather than withholding information from the public. Transparency would remove the need for speculation and help the security community better adapt to NVD's updates. #cybersecurity #infosecurity #riskmanagement #vulnerabilitymanagement

93

3 Comments