Configuration disclosure via traversable ListCategories filename
Published Dec 2, 2024 · Updated Feb 6, 2025
Path traversal in Asterisk 22.0.0 allows remote authenticated users to disclose configuration category names through AMI ListCategories. action_listcategories passes the requester-controlled Filename to ast_config_load2 without first applying the restricted-file check, so ../ segments escape the configuration directory. A valid AMI login with config-class action authorization is required, and the response exposes parsed category names rather than arbitrary raw file bytes.
Summary
What happened
Path traversal in Asterisk 22.0.0 allows remote authenticated users to disclose configuration category names through AMI ListCategories. action_listcategories passes the requester-controlled Filename to ast_config_load2 without first applying the restricted-file check, so ../ segments escape the configuration directory. A valid AMI login with config-class action authorization is required, and the response exposes parsed category names rather than arbitrary raw file bytes.
The record
- CVE
- CVE-2024-53566
- Published
- Dec 2, 2024
- Updated
- Feb 6, 2025
- Vendor
- Asterisk
- Product
- Asterisk
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Feb 6, 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=22.0.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
- AMI ListCategories traversal requestproof of concept · unverified
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