Cloud OAuth secret exposure via hardcoded configuration
Published Jun 26, 2020 · Updated Aug 4, 2024
Hardcoded credentials in Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 allow attackers to obtain the OAuth secret used for cloud communications. The CloudCNM web configuration reads OAUTH_SECRET_KEY from /opt/axess/etc/default/axess, where every affected installation contains the same embedded value. The fixed secret is disclosed in public research, but available sources do not document which cloud operations it authorizes or demonstrate resulting data access or service control.
Summary
What happened
Hardcoded credentials in Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 allow attackers to obtain the OAuth secret used for cloud communications. The CloudCNM web configuration reads OAUTH_SECRET_KEY from /opt/axess/etc/default/axess, where every affected installation contains the same embedded value. The fixed secret is disclosed in public research, but available sources do not document which cloud operations it authorizes or demonstrate resulting data access or service control.
The record
- CVE
- CVE-2020-15331
- Published
- Jun 26, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-311, T1552.001
- 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.
Weakness, pattern, technique
Public exploit references
- Public disclosure of the embedded OAuth secretproof 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