dbcve.org
HertzbeatApplication · Apache

CVE-2024-45505

HIGH · 8.8 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 1.6.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Apache HertzBeat (incubating). This vulnerability can only be exploited by authorized attackers. This issue affects Apache HertzBeat (incubating): 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 · high confidence

Command injection vulnerability in Apache HertzBeat (incubating) allows authorized attackers to execute arbitrary OS commands due to improper neutralization of special elements in input.

MitigationUpgrade to Apache HertzBeat version 1.6.1 or later, which addresses the command injection 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 if Apache HertzBeat is installed
    Check for HertzBeat processes running (ps aux | grep hertzbeat) or look for HertzBeat installation directories, Docker containers, or service configurations.
    Affected if HertzBeat software is found running or installed on the system
  2. Determine the installed HertzBeat version
    Check the version file or startup logs. Common locations: check the pom.xml in installation directory, docker image tag, or run 'hertzbeat --version' if CLI available. Also check the about/page in the web UI.
    Affected if The version number is found to be lower than 1.6.1 (e.g., 1.5.0, 1.4.0, etc.)
  3. Verify if the web interface is accessible
    Attempt to access the HertzBeat web UI (default port 8080 or configured port). Check network configurations and firewall rules.
    Affected if The web interface is exposed and accessible to network attackers
  4. Identify exposed API endpoints
    Review HertzBeat configuration files (application.yml or application.properties) for exposed API settings, especially any endpoints that accept user input and could execute system commands.
    Affected if Any API endpoints accepting user-supplied input are publicly accessible without additional authentication controls

If Apache HertzBeat is installed and the version is below 1.6.1, the environment is affected by this command injection vulnerability.

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 to Apache HertzBeat version 1.6.1 or later, which addresses the command injection vulnerability.

Recommended fix High confidence

1.6.1

  1. Identify the current Hertzbeat version in use
  2. Stop the Hertzbeat service
  3. Backup the current installation and configuration
  4. Download Hertzbeat version 1.6.1 from the official Apache download source
  5. Replace the existing Hertzbeat installation with version 1.6.1
  6. Restore any custom configurations from the backup
  7. Start the Hertzbeat service
  8. Verify the service is running correctly and the web UI is accessible

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

Fix this in Hertzbeat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45505 — 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-45505 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