CVE-2013-1352
Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.
Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.
- Record
CVE-2013-1352- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - CVSS 2.0
- 5.0 Medium
AV:N/AC:L/Au:N/C:P/I:N/A:N - Weakness
- CWE-798
- Updated
- 2026-11-02
CVE List No score
Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.
- Record
CVE-2013-1352- Updated
- 2026-11-02
EUVDEUVD-2013-1391 No score
Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.
- Record
EUVD-2013-1391- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-gcwr-r3hv-m73v No score
Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.
Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.
- Record
GHSA-gcwr-r3hv-m73v- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2013-1352 is a high vulnerability (CVSS 7.5) in Veraxsystems Network Management System, published January 30, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.31%, the 70th percentile. No source names a fixed version.