CVE-2025-61304
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 · uneditedOS command injection vulnerability in Dynatrace ActiveGate ping extension up to 1.016 via crafted ip address.
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 confidenceOS command injection vulnerability in Dynatrace ActiveGate ping extension versions up to 1.016 allows remote attackers to execute arbitrary OS commands by providing a crafted IP address that is not properly sanitized before being passed to a system shell.
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<= 1.016CVSS 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.
-
Verify Dynatrace ActiveGate is installedCheck for the presence of Dynatrace ActiveGate installation directory or running service. On Linux, look in /opt/dynatrace/activegate or check for activegate processes. On Windows, check Program Files/Dynatrace or Windows Services.Affected if Dynatrace ActiveGate is not installed on the system
-
Identify ping extension installation statusLocate the ping extension files within the ActiveGate extensions directory, typically found under <ActiveGate_installation>/extensions/ or via Dynatrace web UI under Extensions > Ping Extension.Affected if The ping extension is not installed or not loaded in ActiveGate
-
Determine ping extension versionCheck the extension manifest file (extension.yaml) or metadata within the ping extension directory for the version number. This file is typically located in the ping extension folder under extensions.Affected if The ping extension version is 1.016 or earlier
-
Verify ping extension is configured with IP address inputsInspect the ping extension configuration (typically extension.yaml, extension.conf, or via Dynatrace web UI monitoring configuration) to see if it is configured to accept and process IP address or hostname parameters for ping targets.Affected if The ping extension is actively configured with IP address or hostname targets that get processed
A system is affected if Dynatrace ActiveGate with the ping extension version 1.016 or lower is installed and configured to accept IP address inputs for ping monitoring.
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 dataUpdate Dynatrace ActiveGate to a version beyond 1.016 that contains the patched code; if immediate patching is not feasible, restrict network access to the ActiveGate and implement input validation on any IP address parameters.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61304 — 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-2025-61304 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