Command injection and data corruption via unvalidated input
Published Oct 16, 2024 · Updated Oct 17, 2024
Improper input validation in RDS Light before 1.1.0 allows remote attackers to inject commands and corrupt stored data. The user-input path in main.py accepts unsanitized content before the framework processes it in memory and API workflows. Exploitation requires an application deployment that exposes the framework to untrusted input; resulting operations can alter cached data or affect API calls.
Summary
What happened
Improper input validation in RDS Light before 1.1.0 allows remote attackers to inject commands and corrupt stored data. The user-input path in main.py accepts unsanitized content before the framework processes it in memory and API workflows. Exploitation requires an application deployment that exposes the framework to untrusted input; resulting operations can alter cached data or affect API calls.
The record
- CVE
- CVE-2024-48918
- Published
- Oct 16, 2024
- Updated
- Oct 17, 2024
- Vendor
- RDSaiPlatforms
- Product
- RDS Light
- Classifications
- CWE-74, CWE-20, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2024CVE publishedPublication date reported by the CVE source.
- Oct 17, 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=< 1.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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