Authenticated SSRF via unchecked HTTP endpoints
Published Jun 30, 2022 · Updated Aug 3, 2024
Server-side request forgery in Jenkins Deployment Dashboard 1.0.10 and earlier allows remote authenticated users to send crafted HTTP requests. Several HTTP endpoints omit permission checks and connect to an attacker-selected URL with attacker-supplied credentials. Overall/Read permission is required, and the controller can be induced to access attacker-selected or internal HTTP services.
Summary
What happened
Server-side request forgery in Jenkins Deployment Dashboard 1.0.10 and earlier allows remote authenticated users to send crafted HTTP requests. Several HTTP endpoints omit permission checks and connect to an attacker-selected URL with attacker-supplied credentials. Overall/Read permission is required, and the controller can be induced to access attacker-selected or internal HTTP services.
The record
- CVE
- CVE-2022-34798
- Published
- Jun 30, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Deployment Dashboard
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=unspecified <=1.0.10
What conditions does exploitation require?
What is affected?
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.
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