🚀 49,000 Patches !

We’ve updated our dataset (https://huggingface.co/datasets/CIRCL/vulnerability-cwe-patch) of real-world vulnerabilities, now enriched with #CWE identifiers and #patches collected from platforms like GitHub, GitLab, Bitbucket.

This dataset is designed to support the development of tools for vulnerability classification. Dataset features are:

- #CVE / #GHSA ID
- Title of the #vulnerability
- Vulnerability description
- Patches (URL, Commit message, and Base64-encoded unified diff)
- CWE categorization

CIRCL/vulnerability-cwe-patch · Datasets at Hugging Face

We’re on a journey to advance and democratize artificial intelligence through open source and open science.

Are all of the Unreviewed GitHub Security Advisories missing package and version range information? Yikes, that's not a fun data curating problem.

https://github.com/advisories/GHSA-x7h6-xxfr-j6pv

#github #ghsa

Could someone on @github's GHSA team please look at these PRs to remove obvious duplicate advisories? It's been a week now and still waiting.

Also this PR which was closed but removes an advisory that just simply references three other advisories affecting a project's dependency. Last time a checked you are not supposed to issue advisories for other advisories; unless you've vendored the vulnerable code.

#github #ghsa

Remove duplicate `camaleon_cms` advisory by postmodern · Pull Request #5622 · github/advisory-database

GHSA-3hp8-6j24-m5gm appears to be the exact same advisory as GHSA-7x4w-cj9r-h4v9, but with slightly different formatting and no CVSS metadata.

GitHub

Anyone at @github's GHSA team care to look into this PR that got closed? I believe I've found an omniauth-saml advisory that simply references three other GHSA advisories that affect one of it's dependencies, ruby-saml. I see no evidence why a separate advisory needs to exist for omniauth-saml, when the security issues exist in ruby-saml, and can easily be upgraded independently of omniauth-saml (ex: gem upgrade ruby-saml / bundle update ruby-saml). This seems like a maintainer created yet another advisory simply to notify their users about other advisories affecting their dependencies, which seems like overkill and creates duplicate security advisory data. I think this GHSA advisory should be withdrawn/removed.
https://github.com/github/advisory-database/pull/5625

#ghsa #omniauth #saml

omniauth-saml | RubyGems.org | your community gem host

Don’t sleep on GHSA! 🛠️ Many security flaws are first disclosed through GitHub Security Advisories — long before they get a CVE. A solid vulnerability management strategy should include GHSA tracking. #CyberSecurity #GHSA #VulnerabilityManagement #DevSecOps
🔒 Vulnerability management isn’t just CVEs — don’t forget GitHub Security Advisories (GHSA)! Many critical issues live only in repos before hitting NVD. Automate GHSA ingestion to stay ahead. #Infosec #VulnManagement #GHSA #DevSecOps
CVE Website

Buckle up everybody, it's another advisory in a popular gem with no patch and slightly inaccurate details. This time affecting all versions of json-jwt:
https://github.com/advisories/GHSA-c8v6-786g-vjx6

The GHSA and NVD entries claim 1.16.3 and below are affected, however the most recent version is 1.16.5, but I reviewed the diffs between the newer versions and don't see significant changes to the logic.

The original advisory was created 2023-12-22, and 1.16.4 was published 2023-12-27, so that checks out as old information. I really wish someone would double check these advisories before they get added to databases.
#ghsa #rubysec

CVE-2023-51774 - GitHub Advisory Database

json-jwt allows bypass of identity checks via a sign/encryption confusion attack

GitHub

More GHSA issues. Appears that the GHSA entries for CVE-2024-26142, CVE-2024-26143, and CVE-2024-26144 incorrectly list the "rails" main gem as being vulnerable, when the actual patches indicate that the actionpack and activestorage gems are vulnerable. Submitted PRs to fix that. Hopefully will get merged quickly so the GHSA data matches what we have in ruby-advisory-db.

My guess is GitHub's advisory importer script might be having some bugs, or someone was in a rush and listed rails because rails is in the advisory titles.
#ghsa #rails #rubysec

CVE-2024-26142 - GitHub Advisory Database

Rails has possible ReDoS vulnerability in Accept header parsing in Action Dispatch

GitHub
[GHSA-785g-282q-pwvx] Rack CORS Middleware has Insecure File Permissions by postmodern · Pull Request #3751 · github/advisory-database

Updates Affected products Comments Only version 2.0.1 of rack-cors is affected. $ gem fetch rack-cors -v 2.0.0 $ tar xvf rack-cors-2.0.0.gem $ tar tzvf data.tar.gz -rw-rw-r-- wheel/wheel 540 ...

GitHub