The most featured CVEs in this week’s security newsletters, with public Proof-of-Concepts, ordered by mention count. Older CVEs and those affecting open source projects with very small userbases aren’t listed.

For the most up-to-date and accurate info, visit the NIST links. Always audit PoCs thoroughly before running them.

CVE-2024-39332

• Severity: Awaiting analysis
• Impacted Products: Webswing 23.2.2
• Description: Webswing 23.2.2 allows remote attackers to modify client-side JavaScript code to achieve path traversal, likely leading to remote code execution via modification of shell scripts on the server.
• Remediation: Follow developer guidance.
• More Info: NVD - CVE-2024-39332
• PoC: https://herolab.usd.de/security-advisories/usd-2024-0008/

CVE-2024-1561

• Severity: Awaiting analysis
• Impacted Products: Gradio 4.12.0 and 3.47 for Python through 4.12 for Python
• Description: An issue was discovered in gradio-app/gradio, where the /component_server endpoint improperly allows the invocation of any method on a Component class with attacker-controlled arguments. Specifically, by exploiting the move_resource_to_block_cache() method of the Block class, an attacker can copy any file on the filesystem to a temporary directory and subsequently retrieve it. This vulnerability enables unauthorized local file read access, posing a significant risk especially when the application is exposed to the internet via launch(share=True), thereby allowing remote attackers to read files on the host machine. Furthermore, gradio apps hosted on huggingface.co are also affected, potentially leading to the exposure of sensitive information such as API keys and credentials stored in environment variables.
• Remediation: Follow developer guidance.
• More Info: NVD - CVE-2024-1561
• PoC: https://github.com/DiabloHTB/CVE-2024-1561/

References

This list was scraped from the quite amazing and highly recommended newsletters below:

• ~this week in security~
• Unsupervised Learning
• @RISK
• Hive Five
• Vulnerable U
• tl;dr sec

Thanks for reading! For corrections, omissions (e.g. newsletter recs) feel free to get in touch.