Read the docs
TI-2013-01188 Aliases CVE-2013-1352GHSA-gcwr-r3hv-m73v

Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.

Priority LOW 35CWE-798Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-798.

Summary

Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.

Why it matters now

EPSS 0.01307 70th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:veraxsystems:network_management_system:*:*:*:*:*:*:*:*before 2.1.0VulnerableVeraxsystems
  • cpe:2.3:a:veraxsystems:network_management_system:*:*:*:*:*:*:*:* Versions before 2.1.0 Vulnerable ·Veraxsystems

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2013-1352
  2. 2026-10-03 Alias added: GHSA-gcwr-r3hv-m73v

References

Advisory 1

  • TI-2013-01186 Verax NMS prior to 2.1.0 has multiple security bypass vulnerabilities CVSS 3.1CRITICAL 9.1
  • TI-2013-01187 Verax NMS prior to 2.10 allows authentication via the encrypted password without knowing the cleartext password. CVSS 3.1MEDIUM 5.9
  • TI-2013-01434 Verax NMS prior to 2.1.0 leaks connection details when any user executes a Repair Table action CVSS 3.1MEDIUM 5.3

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences