CVE-2017-5518: GeniXCMS SSRF in media-file upload feature

CVE-2017-5518 · Severity: high · CVSS 7.4 · Published 2017-01-17

GeniXCMS, a content management system, contains a security flaw in its media upload feature. An attacker can exploit this to force the server to make unauthorized requests to internal systems or external websites. This could allow an attacker to scan private internal networks or interact with internal services that are not intended to be accessible from the internet.

Technologies: Metalgenix Genixcms. Vendors: Metalgenix.

Quick answers

Is CVE-2017-5518 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-5518 being exploited in the wild.
How severe is CVE-2017-5518?
High severity, with a CVSS score of 7.4, published 17 January 2017.
Which products and versions are affected?
GeniXCMS GeniXCMS through 0.0.8.
Is there a fix for CVE-2017-5518?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2017-5518 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2017-5518?
Check whether you run Metalgenix Genixcms. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in GeniXCMS versions up to and including 0.0.8. The vulnerability is located within the media-file upload functionality, which fails to properly validate user-supplied URLs when fetching remote files. A remote attacker can provide a URL pointing to internal network resources (e.g., intranet IP addresses) or loopback interfaces. This allows the attacker to use the server as a proxy to conduct internal port scanning or interact with internal services that are otherwise protected by a firewall. The issue was identified in GitHub issue #64 and is addressed in subsequent patches.

Affected products

  • GeniXCMS GeniXCMS through 0.0.8

Timeline

  • 2017-01-17: disclosed
  • 2017-01-17: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.