Apache Qpid Proton C: Verifying non compliant TLS wildcard cert can cause stack buffer overflow read
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Qpid Proton C, a messaging library used for AMQP communication, is affected when it verifies TLS certificates that use non-compliant wildcard names. Exploitation of this flaw could cause a stack buffer over-read, which may crash the application or expose memory contents, but it does not affect wildcard certificates that follow the RFC 9525 standard.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A misconfigured wildcard TLS certificate causes a stack read overflow. This issue does not affect any wildcard certificate issued to the RFC9525 standard - the fix only accepts certificates that comply to this standard. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Apache Software Foundation Apache Qpid Proton C
through 0.40.0