GHSA-PWJX-QHCG-RVJ4

If a certificate had more than one distributionPoint, then only the first distributionPoint would be considered against each CRL's IssuingDistributionPoint distributionPoint, and then the certificate's subsequent distributionPoints would be ignored.

The impact was that correct provided CRLs would not be consulted to check revocation. With UnknownStatusPolicy::Deny (the default) this would lead to incorrect but safe Error::UnknownRevocationStatus. With UnknownStatusPolicy::Allow this would lead to inappropriate acceptance of revoked certificates.

This vulnerability is thought to be of limited impact. This is because both the certificate and CRL are signed -- an attacker would need to compromise a trusted issuing authority to trigger this bug. An attacker with such capabilities could likely bypass revocation checking through other more impactful means (such as publishing a valid, empty CRL.)

More likely, this bug would be latent in normal use, and an attacker could leverage faulty revocation checking to continue using a revoked credential.

GHSA-PWJX-QHCG-RVJ4 has a CVSS score of 4.4 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.104.0-alpha.5, 0.103.10); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-PWJX-QHCG-RVJ4? GHSA-PWJX-QHCG-RVJ4 is a medium-severity security vulnerability in rustls-webpki (rust), affecting versions >= 0.104.0-alpha.1, < 0.104.0-alpha.5. It is fixed in 0.104.0-alpha.5, 0.103.10.
2. How severe is GHSA-PWJX-QHCG-RVJ4? GHSA-PWJX-QHCG-RVJ4 has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of rustls-webpki are affected by GHSA-PWJX-QHCG-RVJ4? rustls-webpki (rust) versions >= 0.104.0-alpha.1, < 0.104.0-alpha.5 is affected.
4. Is there a fix for GHSA-PWJX-QHCG-RVJ4? Yes. GHSA-PWJX-QHCG-RVJ4 is fixed in 0.104.0-alpha.5, 0.103.10. Upgrade to this version or later.
5. Is GHSA-PWJX-QHCG-RVJ4 exploitable, and should I be worried? Whether GHSA-PWJX-QHCG-RVJ4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-PWJX-QHCG-RVJ4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-PWJX-QHCG-RVJ4?
   • Upgrade rustls-webpki to 0.104.0-alpha.5 or later
   • Upgrade rustls-webpki to 0.103.10 or later