CVE-2025-52574VulnerabilityPublished 24 Jun 2025

CVE-2025-52574: bocaletto-luca elixir-system-monitor · Path Traversal

Affects bocaletto-luca elixir-system-monitorSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.0.1 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade bocaletto-luca/elixir-system-monitor to 1.0.1.

Affected software

Product	Affected	Fixed in
GitHubbocaletto-luca/elixir-system-monitor`pkg:github/bocaletto-luca/elixir-system-monitor`Other threats	Affected <1.0.1	Fixed in 1.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to elixir-system-monitor version 1.0.1 or later, which includes the whitelist patch restricting file reads to the priv/data directory. 2. If immediate upgrade is not feasible, restrict network access to the /read endpoint using firewall rules or network segmentation to limit exposure to trusted internal networks only. 3. Implement Web Application Firewall (WAF) rules to detect and block path traversal patterns in HTTP requests targeting the /read endpoint. 4. Conduct thorough audits of deployed versions of elixir-system-monitor across the environment to identify and remediate vulnerable instances. 5. Monitor logs for unusual access patterns or attempts to read sensitive files via the /read endpoint. 6. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect exploitation attempts in real time. 7. Review and harden file system permissions to minimize the impact of unauthorized file reads, ensuring sensitive files are not world-readable where possible. 8. Educate development and operations teams on secure coding and deployment practices to prevent similar path traversal vulnerabilities in custom or third-party software.

Description

SysmonElixir is a system monitor HTTP service in Elixir. Prior to version 1.0.1, the /read endpoint reads any file from the server's /etc/passwd by default. In v1.0.1, a whitelist was added that limits reading to only files under priv/data. This issue has been patched in version 1.0.1.

Impact

For European organizations deploying elixir-system-monitor versions prior to 1.0.1, this vulnerability poses a significant confidentiality risk. Unauthorized access to files like /etc/passwd can expose user account information, potentially aiding attackers in crafting targeted attacks or escalating privileges. This is particularly critical for organizations managing sensitive infrastructure, including government agencies, financial institutions, and critical infrastructure operators. The ability to remotely exploit this vulnerability without authentication or user interaction increases the attack surface, especially for publicly accessible monitoring services. While the vulnerability does not directly affect system integrity or availability, the information disclosure can be a stepping stone for more severe attacks, including lateral movement and data breaches. European organizations with strict data protection regulations (e.g., GDPR) must consider the reputational and compliance implications of such exposures. Additionally, the presence of this vulnerability in monitoring tools could undermine trust in system telemetry and incident response capabilities.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Jun 2025, 03:24 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats