Internal service access via authority-confused request URLs
Published Sep 6, 2023 · Updated Sep 26, 2024
SSRF in WireMock Studio 2.32.0-17 and earlier allows remote attackers to access server-reachable services through crafted request URLs. Test Requester, webhook, and proxy URL handling appends input directly after http://localhost:8000, allowing an @ character to replace the URI authority. An exposed Studio interface is sufficient; controlled methods, headers, and bodies can reach internal APIs, while Test Requester and proxy mode return their responses.
Summary
What happened
SSRF in WireMock Studio 2.32.0-17 and earlier allows remote attackers to access server-reachable services through crafted request URLs. Test Requester, webhook, and proxy URL handling appends input directly after http://localhost:8000, allowing an @ character to replace the URI authority. An exposed Studio interface is sufficient; controlled methods, headers, and bodies can reach internal APIs, while Test Requester and proxy mode return their responses.
The record
- CVE
- CVE-2023-39967
- Published
- Sep 6, 2023
- Updated
- Sep 26, 2024
- Vendor
- WireMock
- Product
- WireMock
- Classifications
- CWE-918, T1090, T1190
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 6, 2023CVE publishedPublication date reported by the CVE source.
- Sep 26, 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=0 <*
- Affected versionversion=All versions
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
- WireMock Studio Test Requester reproduction procedureproof of concept · demonstrated
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