CVE-2025-61984
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NSummary
CVE-2025-61984 is a low-severity Improper Handling of Invalid Use of Special Elements (CWE-159) vulnerability in Vicarius (inferred from references). Its CVSS base score is 3.6 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 20th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-32089
Vulnerability Data
ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration…
more
file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validity checks on information inputs, directly stopping improper handling of special elements before they affect behavior or integrity.
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.
Secure SDLC practices directly enforce input validation and special-element handling to prevent the weakness.
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.
Security testing can discover the weakness but does not itself implement the preventive control.
Secure development lifecycle mandates input validation and sanitization that directly prevents improper handling of special elements.
Application security requirements explicitly call for controls against malformed or malicious input.
Secure architecture principles reduce attack surface but do not prescribe specific input-filtering techniques.
Secure coding standards require proper escaping, quoting and validation of special characters in user input.