Internal data disclosure via unrestricted Webhook destinations
Published May 22, 2024 · Updated Aug 19, 2024
SSRF in a-blog cms 3.0.x before 3.0.32 and 3.1.x before 3.1.12 allows remote authenticated users to read internal data. The Webhook configuration accepts attacker-chosen request destinations without restricting them to approved hosts, then exposes response data through Webhook logs. Exploitation requires administrator access and HOOK_ENABLE, which is disabled by default, and can disclose local files or otherwise unreachable internal-server information.
Summary
What happened
SSRF in a-blog cms 3.0.x before 3.0.32 and 3.1.x before 3.1.12 allows remote authenticated users to read internal data. The Webhook configuration accepts attacker-chosen request destinations without restricting them to approved hosts, then exposes response data through Webhook logs. Exploitation requires administrator access and HOOK_ENABLE, which is disabled by default, and can disclose local files or otherwise unreachable internal-server information.
The record
- CVE
- CVE-2024-30420
- Published
- May 22, 2024
- Updated
- Aug 19, 2024
- Vendor
- Appleple
- Product
- a-blog cms
- Classifications
- CWE-918, CAPEC-664, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 22, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 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 <3.0.32
- Affected versionversion=0 <3.1.12
- Affected versionversion=prior to Ver.3.0.32
- Affected versionversion=prior to Ver.3.1.12
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