CVE-2025-53077
Samsung Data Management Server Firmware 2.0.0 – 2.3.13.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LSummary
CVE-2025-53077 is a medium-severity EAR (CWE-698) vulnerability in Samsung Data Management Server Firmware. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 24th 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 SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-22976
Vulnerability Data
An execution after redirect in Samsung DMS(Data Management Server) allows attackers to execute limited functions without permissions. An attacker could compromise the integrity of the platform by executing this vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover execution paths that continue after a redirect.
Proper access enforcement reduces the impact of continued execution after a redirect by limiting what the remaining code can do.
Requiring a documented secure development process and standards can mandate exiting immediately after issuing redirects.
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 prevent improper redirect handling via code review and static analysis, but eliminating only this flaw covers a narrow slice of the control's broader intent.
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 detect EAR flaws before deployment.
Secure development lifecycle requires proper handling of redirects and exit logic, reducing EAR risk.
Application security requirements can mandate safe redirect patterns and post-redirect termination.
Secure architecture principles discourage continued execution after redirects.
Secure coding standards directly address proper redirect handling and flow termination.