GHSA-fh2r-99q2-6mmg json
rustls-webpki: CPU denial of service in certificate path building
published 3y ago modified 2mo ago also RUSTSEC-2023-0053
- cvss
- 7.5
- version 3.0, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.
Both TLS clients and TLS servers that accept client certificate are affected.
We now give each path building operation a budget of 100 signature verifications.
The original `webpki` crate is also affected, see [GHSA-8qv2-5vq6-g2g7](https://github.com/advisories/GHSA-8qv2-5vq6-g2g7).
This was previously reported in the original crate <https://github.com/briansmith/webpki/issues/69> and re-reported to us recently.
Patch / fix
- crates.io rustls-webpki 0.100.2, 0.101.4
Is GHSA-fh2r-99q2-6mmg in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | rustls-webpki | <0.100.2 >=0.101.0, <0.101.4 >=0.0.0-0, <0.100.2 |
0.100.2 0.101.4 |
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/rustls/webpki/commit/4ea052366f342a06344aab589565179b59b342d3
web
-
github.com
/rustls/webpki/commit/dcad2406c92169b72c110dd12183fcc74035b683
web
-
github.com
/advisories/GHSA-8qv2-5vq6-g2g7
advisory
-
github.com
/rustls/webpki
package
-
rustsec.org
/advisories/RUSTSEC-2023-0053.html
web, advisory
-
crates.io
/crates/rustls-webpki
package
Sources
- GitHub Advisory GHSA-fh2r-99q2-6mmg
- OSV RUSTSEC-2023-0053
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.