CVE-2024-51358
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 · uneditedAn issue in Linux Server Heimdall v.2.6.1 allows a remote attacker to execute arbitrary code via a crafted script to the Add new application.
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 confidenceA code injection vulnerability exists in the 'Add new application' feature of Heimdall v2.6.1. An unauthenticated remote attacker can submit a crafted script through this feature that gets executed on the server, achieving arbitrary code execution with the privileges of the web application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Heimdall installationConfirm the application is Heimdall by accessing the web interface, checking HTTP response headers for 'Heimdall' references, or locating Heimdall-specific files in the web root directoryAffected if The target is running Heimdall application software
-
Check installed versionLocate the version number in the application (typically visible in the UI footer, in a package.json file, or via API endpoint), then compare it against v2.6.1Affected if The installed version is v2.6.1 or falls within the affected range around this version
-
Verify Add new application feature existsAccess the Heimdall dashboard and navigate to the 'Add new application' section, or check if the endpoint exists via direct URL access (commonly /add or /applications/new)Affected if The 'Add new application' feature is present and accessible in the installation
-
Confirm script input processing is enabledTest whether the Add new application feature accepts and processes custom script content in application configuration fields, or inspect the application's request handling for script execution capabilitiesAffected if The feature accepts and executes script content without sanitization or validation
You are affected if you are running Heimdall v2.6.1 (or an affected version) with the 'Add new application' feature accessible and able to process script input without proper sanitization.
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.
From vendor dataApply any vendor-supplied patch for Heimdall. If no patch is available, disable or restrict the 'Add new application' feature, implement Web Application Firewall rules to block malicious input patterns, and consider network isolation of the Heimdall service.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51358 — 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-51358 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