CVE-2025-48927
Smarsh Telemessage
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2025-48927 is a medium-severity Initialization of a Resource with an Insecure Default (CWE-1188) vulnerability in Smarsh Telemessage. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked in the top 5% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-6 (Configuration Settings) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability CVE-2025-48927 affects the TeleMessage service through version dated 2025-05-05. It stems from an insecure default configuration of Spring Boot Actuator that exposes a heap dump endpoint at the /heapdump URI, corresponding to CWE-1188. This misconfiguration allows unauthenticated network access to potentially sensitive runtime data.
An attacker with network connectivity can retrieve the heap dump without authentication or user interaction, resulting in limited disclosure of information stored in memory. The issue carries a CVSS 3.1 score of 5.3 reflecting low confidentiality impact with no integrity or availability effects.
Public references confirm the flaw was exploited in the wild during May 2025, as documented in the CISA Known Exploited Vulnerabilities catalog and reporting on the TeleMessage compromise. No specific patch or mitigation details are provided in the available references beyond the catalog entry noting active exploitation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-16207
Vulnerability Data
The TeleMessage service through 2025-05-05 configures Spring Boot Actuator with an exposed heap dump endpoint at a /heapdump URI, as exploited in the wild in May 2025.
- CWE(s)
- KEV Date Added
- 01 July 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 13 hardening rules · 7 OS baselines
V14.3.2V6.3.2V11.3.1V13.2.3
Mitigating Controls (NIST 800-53 r5) AI
Baseline configuration directly requires documenting and maintaining secure initial settings instead of insecure defaults.
Configuration settings mandate the most restrictive values be applied at initialization, eliminating reliance on insecure factory defaults.
Least privilege reduces the blast radius of any insecure default permissions that remain after initialization.
Security engineering principles include explicit requirements for secure defaults during resource initialization and design.
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.
Hardened baselines and configuration management directly replace insecure defaults with secure settings.
Secure development practices include designing products with secure defaults rather than insecure ones.
Pre-acquisition integrity checks can reject products known to ship with insecure defaults.
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.
Mandating secure baseline templates and immediate replacement of vendor defaults directly stops systems from being deployed with insecure factory settings that attackers can exploit.
Requiring documented specification, testing, and acceptance of changes ensures that new or modified components are not initialized with insecure default settings that would otherwise be left in production.
Requiring suppliers to document secure configuration and implemented security functions reduces the likelihood that products will be initialised with insecure default settings.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248823 OL 8 must not have the telnet-server package installed. prevents CWE-1188
RHEL 7 (1 rule)
- V-204627 SNMP community strings on the Red Hat Enterprise Linux operating system must be changed from the default. prevents CWE-1188
Ubuntu 22.04 (1 rule)
- V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-1188
Ubuntu 24.04 (1 rule)
- V-270708 Ubuntu 24.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-1188
Windows Server 2016 (1 rule)
- V-224972 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-1188
Windows Server 2019 (1 rule)
- V-205741 Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-1188