Dynatrace Application MonitoringApplication · Jenkins
CVE-2019-10461
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 · uneditedJenkins Dynatrace Application Monitoring Plugin 2.1.3 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system.
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 confidenceThe Jenkins Dynatrace Application Monitoring Plugin versions 2.1.3 and earlier stores credentials in plaintext, unencrypted, within its global configuration file on the Jenkins master node. Users with access to the Jenkins master file system can read these credentials directly from the configuration file.
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
Dynatrace Application MonitoringApplication
<= 2.1.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Dynatrace Application Monitoring Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Dynatrace Application Monitoring' or check the plugins directory for the Dynatrace folderAffected if The plugin appears in the installed list
-
Check plugin versionLocate the plugin version in the plugin's manifest (META-INF/MANIFEST.MF) within the Jenkins plugins directory, or view the version column in Manage Jenkins > Manage Plugins > InstalledAffected if The installed version is 2.1.3 or any version earlier than 2.1.3
-
Identify the plugin's global configuration fileExamine XML configuration files in the Jenkins home directory (JENKINS_HOME) for entries related to the Dynatrace plugin - typically named using the plugin ID such as 'org.jenkinsci.plugins.dynatraceapplicationmonitoring' or similarAffected if A configuration file for this plugin exists in JENKINS_HOME
-
Inspect configuration file for plaintext credentialsOpen the identified configuration file and search for stored credential fields - look for password, apiToken, or similar credential-related XML elements containing visible plaintext values rather than encrypted referencesAffected if The configuration file contains password, token, or credential values stored as plaintext strings (not <encrypted> or credential-binding references)
A user is affected if they have the Dynatrace Application Monitoring Plugin version 2.1.3 or earlier installed and the plugin's configuration file contains unencrypted credential values that could be read from the Jenkins file system.
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 dataImmediately upgrade the Dynatrace Application Monitoring Plugin to a version newer than 2.1.3 if available, rotate any exposed credentials, and restrict filesystem access to the Jenkins master.
Fix this in Dynatrace Application Monitoring
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10461 — 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-2019-10461 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