CVE-2020-15331
First published: Thu Sep 29 2022(Updated: )
Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded OAUTH_SECRET_KEY in /opt/axess/etc/default/axess.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Zyxel CloudCNM SecuManager | =3.1.0 | |
| Zyxel CloudCNM SecuManager | =3.1.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID of this issue?
The vulnerability ID of this issue is CVE-2020-15331.
What is the severity rating of CVE-2020-15331?
CVE-2020-15331 has a severity rating of 9.8 (Critical).
What is the affected software?
The affected software is Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1.
What is the cause of the vulnerability?
The vulnerability is caused by a hardcoded OAUTH_SECRET_KEY in /opt/axess/etc/default/axess.
How can I fix CVE-2020-15331?
To fix CVE-2020-15331, it is recommended to update Zyxel CloudCNM SecuManager to a version that does not have the hardcoded OAUTH_SECRET_KEY.
- collector/nvd-index
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/tags
- agent/description
- agent/type
- agent/event
- agent/softwarecombine
- agent/first-publish-date
- agent/last-modified-date
- vendor/zyxel
- canonical/zyxel cloudcnm secumanager
- version/zyxel cloudcnm secumanager/3.1.0
- version/zyxel cloudcnm secumanager/3.1.1