Sensitive file disclosure via unchecked filename traversal
Published Jun 2, 2025 · Updated Jun 23, 2025
Path traversal in AstrBot 3.4.4 through 3.5.12 allows remote attackers to read sensitive server files via the dashboard file API. The unauthenticated /api/chat/get_file handler joins a supplied filename to the image directory and opens the resulting path without removing traversal sequences or verifying containment. A reachable enabled dashboard is required, and crafted ../ segments can expose LLM API keys, usernames, and password hashes from data/cmd_config.json.
Summary
What happened
Path traversal in AstrBot 3.4.4 through 3.5.12 allows remote attackers to read sensitive server files via the dashboard file API. The unauthenticated /api/chat/get_file handler joins a supplied filename to the image directory and opens the resulting path without removing traversal sequences or verifying containment. A reachable enabled dashboard is required, and crafted ../ segments can expose LLM API keys, usernames, and password hashes from data/cmd_config.json.
The record
- CVE
- CVE-2025-48957
- Published
- Jun 2, 2025
- Updated
- Jun 23, 2025
- Vendor
- AstrBotDevs
- Product
- AstrBot
- Classifications
- CWE-23, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2025CVE publishedPublication date reported by the CVE source.
- Jun 23, 2025Record 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=>= 3.4.4, < 3.5.13
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
- GitHub advisory curl reproductionproof of concept · demonstrated
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