HertzbeatApplication · Apache
CVE-2024-56736
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedServer-Side Request Forgery (SSRF) vulnerability in Apache HertzBeat. This issue affects Apache HertzBeat (incubating): before 1.7.0. Users are recommended to upgrade to version 1.7.0, which fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceServer-Side Request Forgery (SSRF) vulnerability in Apache HertzBeat allows attackers to make the server perform unintended network requests, potentially accessing internal resources or services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
HertzbeatApplication
< 1.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify HertzBeat installation versionCheck the version file or startup logs. Common locations: check the banner output on startup, look for version in the UI (usually in About/Help section), or check the manifest/properties files in the installation directory.Affected if The installed version is below 1.7.0 (e.g., 1.6.x, 1.5.x, etc.)
-
Locate the monitoring target configuration featureIn the HertzBeat web UI, navigate to the monitoring configuration section where users define new monitoring targets. Look for input fields that accept URL or URI values, particularly in features like "API endpoint" monitoring, "HTTP" service checks, or custom URL-based collectors.Affected if The environment has monitoring targets configured with user-controlled URL fields pointing to internal resources (e.g., http://localhost, http://127.0.0.1, http://internal-ip)
-
Review custom collector configurationsCheck if any custom collectors or third-party plugins are configured that accept URL/URI parameters. Examine the YAML configuration files in the <install_dir>/hertzbeat/collectors directory or equivalent custom collector definitions.Affected if Custom collectors exist that accept and process URLs from untrusted input sources without validation
-
Audit HTTP client usage in the applicationReview any HTTP client configurations or proxy settings in the application configuration files (application.yml or application.properties). Look for settings that might allow the server to make outbound HTTP requests based on user input.Affected if HTTP client features are enabled that process URLs from monitoring configurations or user-defined endpoints
A defender is affected if their installed Apache HertzBeat version is below 1.7.0 AND they use features that accept URL/URI inputs from users or monitoring targets.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.7.0
Upgrade Apache HertzBeat to version 1.7.0 or later as recommended in the official advisory.
1.7.0
- 1. Back up your current HertzBeat configuration and data
- 2. Download Apache HertzBeat version 1.7.0 from the official Apache download repository
- 3. Stop the running HertzBeat service
- 4. Install or deploy version 1.7.0 following the standard installation procedure
- 5. Restore your backed-up configuration
- 6. Start the HertzBeat service
- 7. Verify the service is running correctly and SSRF vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Hertzbeat
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56736 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-56736 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data