dbcve.org
Vmware Lab Manager SlavesApplication · Jenkins

CVE-2019-1003079

MEDIUM · 6.5 CVSS v3.1 Published 2019-04-04
Fix available
A fix is available. Upgrade to after 0.2.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A missing permission check in Jenkins VMware Lab Manager Slaves Plugin in the LabManager.DescriptorImpl#doTestConnection form validation method allows attackers with Overall/Read permission to initiate a connection to an attacker-specified server.

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 confidence

A missing permission check in the Jenkins VMware Lab Manager Slaves Plugin's LabManager.DescriptorImpl#doTestConnection form validation method allows any user with Overall/Read permission (the lowest privilege) to make the Jenkins server initiate connections to attacker-specified servers. This is a Server-Side Request Forgery (SSRF) vulnerability where authentication exists but authorization is missing.

MitigationApply the security fix to the VMware Lab Manager Slaves Plugin which adds proper permission checking to the doTestConnection method. Until patched, restrict user permissions and consider network segmentation to limit SSRF impact.

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
Vmware Lab Manager SlavesApplication
Affected:<= 0.2.8

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if VMware Lab Manager Slaves plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'VMware Lab Manager Slaves' or 'labmanager', or list installed plugins via Jenkins CLI: java -jar jenkins-cli.jar list-plugins
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the Manage Plugins > Installed tab, find the Version column for the VMware Lab Manager Slaves plugin, or inspect the plugin's manifest.xml in Jenkins home directory under plugins/lab-manager-slaves/
    Affected if The version is 0.2.8 or any version lower than 0.2.8
  3. Identify users with Overall/Read permission
    Navigate to Manage Jenkins > Manage Users and review user accounts; check Manage Jenkins > Configure Global Security to see authorization strategy and which users/groups are granted Overall/Read access
    Affected if There are users with Overall/Read permission who should not have the ability to trigger server connections to arbitrary hosts
  4. Verify the doTestConnection form validation is accessible
    Check if the endpoint /descriptorByName/LabManager.DescriptorImpl/doTestConnection responds to requests from users with only Overall/Read permission by reviewing the plugin configuration page at Manage Jenkins > Configure System > VMware Lab Manager Slaves
    Affected if The form validation can be triggered by a user who only has Overall/Read permission (the lowest privilege level)

You are affected if the VMware Lab Manager Slaves plugin is installed at version 0.2.8 or lower AND your Jenkins instance has users with Overall/Read permission who should not be able to trigger outbound connections from the server.

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
Upgrade available Upgrade to a release after 0.2.8
Interim mitigation

Apply the security fix to the VMware Lab Manager Slaves Plugin which adds proper permission checking to the doTestConnection method. Until patched, restrict user permissions and consider network segmentation to limit SSRF impact.

Fix this in Vmware Lab Manager Slaves Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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