Absint AstreeApplication · Jenkins
CVE-2018-1000189
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 · uneditedA command execution vulnerability exists in Jenkins Absint Astree Plugin 1.0.5 and older in AstreeBuilder.java that allows attackers with Overall/Read access to execute a command on the Jenkins master.
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 confidenceA command injection vulnerability exists in the Absint Astree Jenkins plugin (versions 1.0.5 and older) through the AstreeBuilder.java component. Attackers with basic Overall/Read access to Jenkins can execute arbitrary commands on the master server, achieving remote code execution with the privileges of the Jenkins process.
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
Absint AstreeApplication
<= 1.0.5CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/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 if Absint Astree plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the JENKINS_HOME/plugins directory for the 'absint-astree' folderAffected if The Absint Astree plugin folder or entry exists in the Jenkins plugins directory
-
Determine the installed version of Absint AstreeIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find Absint Astree and read the Version column; alternatively, check the version file in JENKINS_HOME/plugins/absint-astree/META-INF/MANIFEST.MFAffected if The installed version is 1.0.5 or older
-
Identify jobs using the Absint Astree builderSearch Jenkins job configurations for the AstreeBuilder step: use Jenkins script console with 'Jenkins.instance.allItems' to find jobs containing 'AstreeBuilder' in their configuration XML, or manually review job configurationsAffected if Any job is configured to use the Absint Astree build step
-
Check Jenkins user permissionsReview which users or groups have Overall/Read permission in Jenkins > Manage Jenkins > Configure Global Security > AuthorizationAffected if Users other than administrators have Overall/Read access enabled
A user is affected if the Absint Astree plugin version 1.0.5 or older is installed and any user with Overall/Read permission exists in the Jenkins instance.
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 the Absint Astree Plugin to a version newer than 1.0.5. If no patched version is available, remove the plugin entirely from the Jenkins instance to eliminate the attack vector.
Fix this in Absint Astree
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000189 — 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-2018-1000189 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