dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-53577

CRITICAL · 10.0 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Control of Generation of Code ('Code Injection') vulnerability in thehp Global DNS global-dns allows Remote Code Inclusion.This issue affects Global DNS: from n/a through <= 3.1.0.

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

Code injection vulnerability in HP Global DNS global-dns allows remote attackers to inject and execute arbitrary code on the target system. The improper control of code generation enables Remote Code Inclusion (RCI), making complete system compromise likely.

MitigationUpgrade HP Global DNS to a version beyond 3.1.0 that contains the patch for this vulnerability. If no patched version is available, implement strict input validation and network segmentation to limit exposure.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 HP Global DNS global-dns is installed
    Search for the global-dns binary or service on the system using commands like 'which global-dns', 'ls /usr/bin/*dns*', or check system service lists
    Affected if The product is not found in the system - not affected
  2. Determine the installed version of global-dns
    Run 'global-dns --version' or 'global-dns -v' to retrieve the version number; if not available, check installed package metadata
    Affected if Version is 3.1.0 or lower (any version through 3.1.0 is affected)
  3. Verify network exposure of the DNS service
    Check listening network ports and firewall rules for the DNS service interface (typically port 53 UDP/TCP) and determine if it accepts untrusted external input
    Affected if The DNS interface is accessible from untrusted networks - vulnerable to remote exploitation
  4. Inspect configuration files for remote include capabilities
    Review global-dns configuration files in /etc/global-dns/ or similar paths for settings that allow remote parameter injection or dynamic code execution
    Affected if Configuration permits user-controlled parameters to influence code generation paths

The environment is affected if HP Global DNS global-dns version 3.1.0 or lower is installed and the DNS interface is network-accessible to potential attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HP Global DNS to a version beyond 3.1.0 that contains the patch for this vulnerability. If no patched version is available, implement strict input validation and network segmentation to limit exposure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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