Event signature forgery via credential cache collision
Published Jan 22, 2025 · Updated Mar 20, 2025
Incorrect authorization in Jenkins Eiffel Broadcaster Plugin 2.8.0 through 2.10.2 allows remote authenticated users to sign RabbitMQ events. A signing-data cache indexes certificate material only by credential ID, so an attacker-controlled credential in another store collides with and reuses the legitimate cached material. Signing must be explicitly enabled, and exploitation requires permission to create a same-ID credential in a different Jenkins credentials store.
Summary
What happened
Incorrect authorization in Jenkins Eiffel Broadcaster Plugin 2.8.0 through 2.10.2 allows remote authenticated users to sign RabbitMQ events. A signing-data cache indexes certificate material only by credential ID, so an attacker-controlled credential in another store collides with and reuses the legitimate cached material. Signing must be explicitly enabled, and exploitation requires permission to create a same-ID credential in a different Jenkins credentials store.
The record
- CVE
- CVE-2025-24400
- Published
- Jan 22, 2025
- Updated
- Mar 20, 2025
- Vendor
- Jenkins Project
- Product
- Eiffel Broadcaster
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 22, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.8.0 <=2.10.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo