Unauthenticated SSRF via unrestricted console server address
Published May 13, 2024 · Updated Feb 13, 2025
SSRF in SRS 4.0.195 and 4.0.268 allows remote attackers to induce outbound requests via a crafted console server address. The Connect SRS workflow accepts an attacker-controlled server IP and sends an API version request to that destination without a target allowlist. No authentication is reported; the demonstrated consequence is a server-originated HTTP request, while arbitrary code execution is not substantiated by the disclosure.
Summary
What happened
SSRF in SRS 4.0.195 and 4.0.268 allows remote attackers to induce outbound requests via a crafted console server address. The Connect SRS workflow accepts an attacker-controlled server IP and sends an API version request to that destination without a target allowlist. No authentication is reported; the demonstrated consequence is a server-originated HTTP request, while arbitrary code execution is not substantiated by the disclosure.
The record
- CVE
- CVE-2024-33250
- Published
- May 13, 2024
- Updated
- Feb 13, 2025
- Vendor
- Open Source SRS Community
- Product
- SRS (Simple Realtime Server)
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=4.0.195
- Affected versionversion=4.0.268
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
- DNS and netcat callback proof of conceptproof 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