Cyber Resilience

CVE-2025-5485

Published
12 June 2025
Modified
17 June 2026
CVSS Score v4 8.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/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.0041 34th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2025-5485 is a high-severity Observable Response Discrepancy (CWE-204) vulnerability in Cisa (inferred from references). Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Account Discovery (T1087); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-6 (Authentication Feedback) and SI-11 (Error Handling) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

User names used to access the web management interface are limited to the device identifier, which is a numerical identifier no more than 10 digits. A malicious actor can enumerate potential targets by incrementing or decrementing from known identifiers or…

more

through enumerating random digit sequences.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1087.001 Local Account Discovery
Adversaries may attempt to get a listing of local system accounts.
T1087.002 Domain Account Discovery
Adversaries may attempt to get a listing of domain accounts.
T1087.003 Email Account Discovery
Adversaries may attempt to get a listing of email addresses and accounts.
T1087.004 Cloud Account Discovery
Adversaries may attempt to get a listing of cloud accounts.
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-3092Shared CWE-204
CVE-2025-62512Shared CWE-204
CVE-2025-34155Shared CWE-204
CVE-2025-66307Shared CWE-204
CVE-2026-24097Shared CWE-204
CVE-2025-30280Shared CWE-204
CVE-2025-54129Shared CWE-204
CVE-2026-53908Shared CWE-204
CVE-2026-30876Shared CWE-204
CVE-2025-9824Shared CWE-204

Affected Assets

Cisa
inferred from references and description; NVD did not file a CPE for this CVE

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)
  • V13.4.5

Mitigating Controls (NIST 800-53 r5) AI

Obscuring authentication feedback directly stops one common source of observable response discrepancies.

Error handling explicitly requires messages that avoid revealing exploitable internal information.

Information flow enforcement can block responses that would otherwise disclose internal state to unauthorized parties.

Boundary protection monitors and filters outbound responses that could leak internal state.

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 full match
prevents

Secure SDLC practices directly prevent introduction of inconsistent response behavior that leaks internal state.

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.

finds

Security testing can detect observable response discrepancies before deployment.

mitigates

Network security controls can enforce uniform responses and suppress observable discrepancies.

prevents

Secure SDLC practices include error-handling and response standardization to avoid information disclosure.

prevents

Application security requirements typically mandate consistent, non-revealing error messages.

prevents

Secure architecture principles discourage designs that leak internal state via differing responses.

prevents

Secure coding standards explicitly require uniform error handling to prevent information leakage.

References