CVE-2020-15331 json
Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded OAUTH_SECRET_KEY in /opt/axess/etc/default/axess.
published 6y ago modified 4mo ago also EUVD-2020-7328
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded OAUTH_SECRET_KEY in /opt/axess/etc/default/axess.
Is CVE-2020-15331 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- pierrekim.github.io https://pierrekim.github.io/blog/2020-03-09-zyxel-secumanager-0day-vulnerabilities.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Classification
- Weakness
-
- CWE-311 Missing Encryption of Sensitive Data
References
-
pierrekim.github.io
/blog/2020-03-09-zyxel-secumanager-0day-vulnerabilities.html
exploit, third-party-advisory
-
zyxel.com
/support/vulnerabilities-of-CloudCNM-SecuManager.shtml
vendor-advisory
Sources
- CVE List CVE-2020-15331
- NVD CVE-2020-15331
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.