Azure Vm AgentsApplication · Jenkins
CVE-2019-1003037
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 information exposure vulnerability exists in Jenkins Azure VM Agents Plugin 0.8.0 and earlier in src/main/java/com/microsoft/azure/vmagent/AzureVMCloud.java that allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
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 Azure VM Agents Plugin for Jenkins versions 0.8.0 and earlier exposes credential IDs stored in Jenkins through the AzureVMCloud component. Any user with Overall/Read permission can enumerate these credential IDs, potentially aiding attackers in identifying valid credentials to target for further exploitation.
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
Azure Vm AgentsApplication
<= 0.8.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check if Azure VM Agents plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Azure VM Agents', or inspect the $JENKINS_HOME/plugins directory for a folder named azure-vm-agentsAffected if Plugin is present in Jenkins
-
Verify the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, find the Azure VM Agents plugin and note the version number; alternatively, locate the manifest file (META-INF/MANIFEST.MF) inside the plugin's .hpi file to read the Implementation-VersionAffected if Version is 0.8.0 or earlier
-
Confirm AzureVMCloud configuration existsNavigate to Manage Jenkins > Manage Nodes and Clouds > Clouds, or inspect the Jenkins configuration file (usually $JENKINS_HOME/config.xml) for <azureVMCloud> elementsAffected if AzureVMCloud cloud configuration is defined in Jenkins
-
Check for exposed credential IDs in AzureVMCloudReview the AzureVMCloud configuration output via the API or UI; the vulnerability exposes credential IDs (not the secrets themselves) which can be retrieved by any user with Overall/Read access through the AzureVMCloud componentAffected if AzureVMCloud is configured and exposes credential IDs to users with read access
User is affected if Azure VM Agents plugin version 0.8.0 or earlier is installed AND AzureVMCloud is configured, allowing any user with Overall/Read permission to enumerate stored credential IDs.
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 dataUpgrade Azure VM Agents Plugin to a version beyond 0.8.0. Until patched, restrict Overall/Read permission to only trusted administrators and audit user access.
Fix this in Azure Vm Agents
Scoped from the published advisory
- 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-2019-1003037 — 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-1003037 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