CVE-2016-3718
Server-Side Request Forgery (SSRF) in The (1) HTTP and (2) FTP coders in ImageMagick before 6
Executive Summary
CVE-2016-3718 is a medium severity vulnerability affecting api-security. It is classified as Server-Side Request Forgery. This vulnerability is actively being exploited in the wild.
Precogs AI Insight
"The ImageMagick HTTP and FTP coders are vulnerable to Server-Side Request Forgery (SSRF). Attackers upload crafted images containing embedded URLs to scan internal networks or extract metadata. Precogs API Security Engine detects unconstrained outbound requests initiated by backend processing."
What is this vulnerability?
CVE-2016-3718 is categorized as a medium Server-Side Request Forgery (SSRF) flaw with a CVSS base score of 5.5. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.
The (1) HTTP and (2) FTP coders in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allow remote attackers to conduct server-side request forgery (SSRF) attacks via a crafted image.
This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.
Risk Assessment
| Metric | Value |
|---|---|
| CVSS Base Score | 5.5 (MEDIUM) |
| Vector String | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| Published | May 5, 2016 |
| Last Modified | April 22, 2026 |
| Related CWEs | CWE-918, CWE-918 |
Impact on Systems
✅ Unauthorized Data Access: Attackers can bypass authorization controls to access other users' data or administrative endpoints.
✅ Account Takeover: Broken authentication or authorization may enable full account compromise without valid credentials.
✅ API Abuse: Exploiting this vulnerability enables mass data harvesting or destructive operations through unprotected API endpoints.
How to Fix and Mitigate CVE-2016-3718
- Apply Vendor Patches Immediately: This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog. Apply updates per vendor instructions.
- Verify Patch Deployment: Confirm all instances are updated using Precogs continuous monitoring.
- Review Audit Logs: Investigate historical access logs for indicators of compromise related to this attack surface.
- Implement Defense-in-Depth: Deploy WAF rules, network segmentation, and endpoint detection to limit blast radius.
Defending with Precogs AI
The ImageMagick HTTP and FTP coders are vulnerable to Server-Side Request Forgery (SSRF). Attackers upload crafted images containing embedded URLs to scan internal networks or extract metadata. Precogs API Security Engine detects unconstrained outbound requests initiated by backend processing.
Use Precogs to continuously scan your codebase, binaries, APIs, and infrastructure for this vulnerability class and related attack patterns. Our AI-powered detection engine combines static analysis with threat intelligence to identify exploitable weaknesses before attackers do.
Vulnerability Code Signature
Attack Data Flow
| Stage | Detail |
|---|---|
| Source | User-supplied URL parameter |
| Vector | Server fetches the user-controlled URL |
| Sink | HTTP request library (e.g., fetch, axios) |
| Impact | Access to internal services, metadata endpoints, or port scanning |
Vulnerable Code Pattern
// ❌ VULNERABLE: Server-Side Request Forgery
app.get('/proxy', async (req, res) => {
const targetUrl = req.query.url;
// Taint sink: unvalidated outbound request
const response = await fetch(targetUrl);
res.send(await response.text());
});
Secure Code Pattern
// ✅ SECURE: Allowlist validation
const ALLOWED_DOMAINS = ['api.partner.com'];
app.get('/proxy', async (req, res) => {
const targetUrl = new URL(req.query.url);
if (!ALLOWED_DOMAINS.includes(targetUrl.hostname)) {
return res.status(403).send("Domain not allowed");
}
// Sanitized outbound request
const response = await fetch(targetUrl.href);
res.send(await response.text());
});
How Precogs Detects This
Precogs API Security Engine actively detects SSRF vulnerabilities by tracking unvalidated URL sinks and enforcing strict allowlist policies.\n