RUSTSEC-2022-0065

Source
https://rustsec.org/advisories/RUSTSEC-2022-0065
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2022-0065.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2022-0065
Aliases
Published
2022-11-01T12:00:00Z
Modified
2023-12-06T01:02:31.170840Z
Summary
X.509 Email Address Variable Length Buffer Overflow
Details

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the . character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service).

In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Database specific
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / openssl-src

Package

Affected ranges

Type
SEMVER
Events
Introduced
300.0.0
Fixed
300.0.11

Ecosystem specific

{
    "affected_functions": null,
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific

{
    "cvss": null,
    "informational": null,
    "categories": [
        "denial-of-service"
    ]
}