CVE intelligence and bounded remediation

CVE-2013-1352 — Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive

High CVSS 7.5

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

Severity
High
CVSS
7.5 (3.1)
Published
2020-01-30
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-798

Affected products

  • veraxsystems / network_management_system

Matched remediation archetype

Authentication bypass and missing authentication

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map every affected endpoint and protocol path, including alternate ports, legacy routes, recovery flows, service accounts, and machine-to-machine access.
  • Confirm which deployments enable the affected authentication mode and whether the interface is reachable from untrusted networks.
  • Review session, token, credential, and proxy trust configuration without attempting account takeover.

Remediate safely

  • Apply the supported fix and centralize fail-closed authentication before protected request handling.
  • Remove default or embedded credentials, rotate affected secrets and sessions, and bind authentication decisions to the intended audience and channel.
  • Add negative tests for alternate routes, malformed or absent credentials, recovery flows, and proxy-derived identity.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.