Add advisory: asn1 BerReader infinite loop CPU DoS (CWE-835)#7561
Add advisory: asn1 BerReader infinite loop CPU DoS (CWE-835)#7561tynus3 wants to merge 3 commits into
Conversation
|
This is a new issue without an existing GHSA ID. The CI failure ("unable to match file to existing advisory") is expected — I understand the normal contribution process requires an existing GHSA entry. Could a GitHub staff member create a draft GHSA for npm/asn1 so I can update it, or advise on the correct intake process for new untracked vulnerabilities? The package is unmaintained (last release Nov 2021) so there is no maintainer to file a private advisory with. |
|
👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the |
|
Hi @tynus3, per the GHAD's contributing guidelines isn't for coordinating disclosure or for escalating a case where a maintainer is unresponsive. Because GitHub's CNA scope limits us to "CVEs requested by code owners using the GitHub Security Advisories feature," you'll need to go to a CNA that is not GitHub, such as MITRE (https://cveform.mitre.org), to receive a CVE. |
New vulnerability in npm package
asn1v0.2.6 (latest).Downstream confirmed affected: sshpk (21.9M/week), ldapjs (322k/week, decommissioned),
@ldapjs/asn1 (204k/week, decommissioned). Separate advisories for those to follow.
No CVE assigned yet — requesting GHSA ID assignment.