Is CVE-2017-5539 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2017-5539 being exploited in the wild.

How severe is CVE-2017-5539?

Critical severity, with a CVSS score of 9.1, published 23 January 2017.

Which products and versions are affected?

b2evolution b2evolution 6.8.4-stable.

Is there a fix for CVE-2017-5539?

A patch was published on 2017-01-19: Version 6.8.5-stable released with security fixes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2017-5539 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2017-5539?

Check whether you run B2evolution. 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.

CVE-2017-5539: b2evolution directory traversal bypass in file management

CVE-2017-5539 · Severity: critical · CVSS 9.1 · Published 2017-01-23

A security flaw in the b2evolution content management system allows unauthorized users to access or delete sensitive files on the web server. This occurs because a previous security patch was incomplete, allowing attackers to bypass restrictions and manipulate files they should not have access to. This could lead to the theft of private data, website defacement, or a total loss of site functionality.

Technologies: B2evolution. Vendors: B2evolution.

Quick answers

Is CVE-2017-5539 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-5539 being exploited in the wild.
How severe is CVE-2017-5539?: Critical severity, with a CVSS score of 9.1, published 23 January 2017.
Which products and versions are affected?: b2evolution b2evolution 6.8.4-stable.
Is there a fix for CVE-2017-5539?: A patch was published on 2017-01-19: Version 6.8.5-stable released with security fixes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-5539 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2017-5539?: Check whether you run B2evolution. 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 path traversal vulnerability exists in b2evolution version 6.8.4-stable due to an incomplete fix for a previous traversal issue (CVE-2017-5480). An attacker can bypass the existing filter rules by using specific character sequences like '..\\/' in file paths. This allows for unauthenticated remote attackers to perform arbitrary file reads, file deletions, or verify the existence of files on the underlying filesystem. The issue was addressed in version 6.8.5-stable by improving the sanitization of user-supplied path inputs.

Affected products

b2evolution b2evolution 6.8.4-stable

Timeline

2017-01-17: disclosed: Issue reported to vendor via GitHub and email
2017-01-19: patched: Version 6.8.5-stable released with security fixes
2017-01-23: advisory: NVD publication date

References

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