Authenticated data disclosure via OSS configuration SSRF
Published Apr 16, 2025 · Updated Apr 16, 2025
Server-side request forgery in Apache HertzBeat before 1.7.0 allows remote authenticated users to read network-accessible data via OSS configuration. The OSS configuration API causes the server to contact an attacker-selected destination, but Apache has not disclosed the affected handler or missing validation. A valid HertzBeat account is required, and the published impact is limited to confidentiality rather than data modification or service interruption.
Summary
What happened
Server-side request forgery in Apache HertzBeat before 1.7.0 allows remote authenticated users to read network-accessible data via OSS configuration. The OSS configuration API causes the server to contact an attacker-selected destination, but Apache has not disclosed the affected handler or missing validation. A valid HertzBeat account is required, and the published impact is limited to confidentiality rather than data modification or service interruption.
The record
- CVE
- CVE-2024-56736
- Published
- Apr 16, 2025
- Updated
- Apr 16, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache HertzBeat
- Classifications
- CWE-918, CAPEC-664, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=0 <1.7.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