Security Resilience

CVE-2023-23903

Nozominetworks Cmc ≤ 22.6.2

Published
09 August 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0060 48th percentile
Risk Priority 28 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-23903 is a medium-severity Improper Validation of Syntactic Correctness of Input (CWE-1286) vulnerability in Nozominetworks Cmc. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An authenticated administrator can upload a SAML configuration file with the wrong format, with the application not checking the correct file format. Every subsequent application request will return an error. The whole application in rendered unusable until a console intervention.

CWE(s)
CWE-1286NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
attack.mitre.org →
T1011.001 Exfiltration Over Bluetooth Exfiltration
Adversaries may attempt to exfiltrate data over Bluetooth rather than the command and control channel.
attack.mitre.org →
T1014 Rootkit Stealth
Adversaries may use rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components.
attack.mitre.org →
T1016.002 Wi-Fi Discovery Discovery
Adversaries may search for information about Wi-Fi networks, such as network names and passwords, on compromised systems.
attack.mitre.org →
T1021.003 Distributed Component Object Model Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
attack.mitre.org →
T1021.004 SSH Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-24015Same product: Nozominetworks Cmc
CVE-2023-32649Same product: Nozominetworks Cmc
CVE-2025-40889Same product: Nozominetworks Cmc
CVE-2025-40885Same product: Nozominetworks Cmc
CVE-2023-29245Same product: Nozominetworks Cmc
CVE-2025-40887Same product: Nozominetworks Cmc
CVE-2025-3718Same product: Nozominetworks Cmc
CVE-2025-40898Same product: Nozominetworks Cmc
CVE-2025-40886Same product: Nozominetworks Cmc
CVE-2025-40888Same product: Nozominetworks Cmc

Affected Assets

nozominetworks
cmc
≤ 22.6.2
nozominetworks
guardian
≤ 22.6.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.2
  • V2.2.2
  • V3.5.5
  • V5.4.1

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly require syntactic input validation to prevent malformed data handling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach syntactic validation defects, but leaves a bounded remainder (e.g. incomplete enforcement across all parsers, second-order inputs, or outsourced components where assurance is only obtained not enforced).

A.8.26 Application security requirements partial match
blocks

Application security requirements explicitly call for validation of input syntax.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates security engineering principles including data validation/sanitization, distrust external input, security by design, and design reviews against attack patterns, which directly stops syntactic validation flaws from reaching production in most cases; the bounded remainder is incomplete application to outsourced development, legacy code, or post-design changes.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper syntactic validation of all inputs.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development catches missing or incorrect syntax validation.

A.8.8 Management of technical vulnerabilities partial match
removes

References