Traffic decryption via hardcoded Ejabberd private key
Published Jun 26, 2020 · Updated Aug 4, 2024
Hardcoded cryptographic key in Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 allows remote attackers to decrypt Ejabberd traffic. The Ejabberd TLS configuration loads the same embedded RSA private key and certificate from ejabberd.pem on affected installations. A man-in-the-middle position on the XMPP path is required, exposing confidentiality of CPE management traffic without altering it.
Summary
What happened
Hardcoded cryptographic key in Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 allows remote attackers to decrypt Ejabberd traffic. The Ejabberd TLS configuration loads the same embedded RSA private key and certificate from ejabberd.pem on affected installations. A man-in-the-middle position on the XMPP path is required, exposing confidentiality of CPE management traffic without altering it.
The record
- CVE
- CVE-2020-15326
- Published
- Jun 26, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Published Ejabberd RSA private keyproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo