Improper Verification of Cryptographic Signature The advisory has been revoked - it doesn't affect any version of package aspnetcore-targeting-pack-5.0 (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS8-ASPNETCORETARGETINGPACK50-2432592
- published24 Mar 2022
- disclosed18 Mar 2022
Introduced: 18 Mar 2022
CVE-2022-24772 (opens in a new tab)Amendment
The Centos security team deemed this advisory irrelevant for Centos:8.
NVD Description
Note: Versions mentioned in the description apply only to the upstream aspnetcore-targeting-pack-5.0 package and not the aspnetcore-targeting-pack-5.0 package as distributed by Centos.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not check for tailing garbage bytes after decoding a DigestInfo ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used. The issue has been addressed in node-forge version 1.3.0. There are currently no known workarounds.
References
- https://access.redhat.com/security/cve/CVE-2022-24772
- https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1
- https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2
- https://github.com/digitalbazaar/forge/security/advisories/GHSA-x4jg-mjrx-434g