Authenticated SSRF via image proxy URL
Published Feb 19, 2025 · Updated Feb 19, 2025
Server-side request forgery in Pigeon 1.0.177 allows remote authenticated users to read resources reachable by the image proxy. The imgproxy/index.php handler base64-decodes the url parameter and passes the accepted result to cURL with redirect following enabled, causing the server to perform the fetch. A valid session-derived token is required, and the confirmed consequence is limited to reading data reachable from the server.
Summary
What happened
Server-side request forgery in Pigeon 1.0.177 allows remote authenticated users to read resources reachable by the image proxy. The imgproxy/index.php handler base64-decodes the url parameter and passes the accepted result to cURL with redirect following enabled, causing the server to perform the fetch. A valid session-derived token is required, and the confirmed consequence is limited to reading data reachable from the server.
The record
- CVE
- CVE-2025-1447
- Published
- Feb 19, 2025
- Updated
- Feb 19, 2025
- Vendor
- kasuganosoras
- Product
- Pigeon
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 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=1.0.177
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.
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