dbcve.org
HertzbeatApplication · Apache

CVE-2024-45791

HIGH · 7.5 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 1.6.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache HertzBeat. This issue affects Apache HertzBeat: before 1.6.1. Users are recommended to upgrade to version 1.6.1, 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 confidence

Apache HertzBeat versions before 1.6.1 contain an information disclosure vulnerability allowing unauthorized actors to access sensitive information. The specific nature of the exposed data is not detailed in the advisory, but the HIGH CVSS score indicates significant risk.

MitigationUpgrade Apache HertzBeat to version 1.6.1 or later to remediate this vulnerability.

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
Affected:< 1.6.1

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify HertzBeat installation and version
    Locate the HertzBeat installation directory and check the version file or startup logs. Common locations: check the 'VERSION' file in the installation root, or look for version info in startup logs (startup.log or console output). If running via Docker, run 'docker ps' and check image tags, or use 'docker exec <container> cat VERSION' if available.
    Affected if The installed version number is lower than 1.6.1 (e.g., 1.5.0, 1.4.0, etc.)
  2. Verify the web interface is accessible
    Determine if the HertzBeat web UI or API endpoints are exposed to the network. Check the application configuration file (typically application.yml or application.properties in the config directory) for server.bind-address or server.port settings, and confirm whether the service is bound to 0.0.0.0 or an externally accessible IP rather than localhost only.
    Affected if The web interface/API is accessible from untrusted networks without proper authentication restrictions in place
  3. Review access logs for unauthorized queries
    Examine HertzBeat access logs (typically found in logs/access.log or logs/hertzbeat.log within the installation directory) for suspicious or unauthorized API requests, especially those targeting sensitive endpoints, configuration files, or data export features that occurred before the version was patched.
    Affected if There are access log entries showing requests from unauthorized IP addresses or unusual patterns accessing sensitive data endpoints

You are affected if your deployed Apache HertzBeat version is any version prior to 1.6.1 and the web interface or API is network-accessible to unauthorized users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.6.1 or later
Fixed in 1.6.1
Interim mitigation

Upgrade Apache HertzBeat to version 1.6.1 or later to remediate this vulnerability.

Recommended fix High confidence

1.6.1

  1. 1. Back up your current Hertzbeat configuration and data
  2. 2. Download Apache HertzBeat version 1.6.1 from the official Apache download repository
  3. 3. Stop the currently running Hertzbeat service
  4. 4. Install or deploy version 1.6.1
  5. 5. Restore your configuration from the backup if needed
  6. 6. Start the Hertzbeat service
  7. 7. Verify the service is running correctly and the sensitive information exposure is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hertzbeat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45791 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45791 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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