Unspecified impact via nondirectory path reuse
Published Jun 16, 2024 · Updated Oct 30, 2024
Improper path validation in irodsServerMonPerf in iRODS before 4.3.2 allows remote attackers to trigger use of a nondirectory path. The script continues with an encountered filesystem path after the directory check fails, rather than terminating the operation. CISA rates the flaw network-reachable without authentication, but upstream material does not disclose the exact integrity consequence.
Summary
What happened
Improper path validation in irodsServerMonPerf in iRODS before 4.3.2 allows remote attackers to trigger use of a nondirectory path. The script continues with an encountered filesystem path after the directory check fails, rather than terminating the operation. CISA rates the flaw network-reachable without authentication, but upstream material does not disclose the exact integrity consequence.
The record
- CVE
- CVE-2024-38461
- Published
- Jun 16, 2024
- Updated
- Oct 30, 2024
- Vendor
- iRODS Consortium
- Product
- iRODS
- Classifications
- CWE-754
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.3.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo