CVE-2017-5539
UnknownEPSS 4.14%
Last modified
CVE-2017-5539 is a vulnerability of currently unknown severity. The patch for directory traversal (CVE-2017-5480) in b2evolution version 6.8.4-stable has a bypass vulnerability. An attacker can use ..\/ to bypass the filter rule. EPSS estimates a 4.14% chance of exploitation in the next 30 days.
Description
The patch for directory traversal (CVE-2017-5480) in b2evolution version 6.8.4-stable has a bypass vulnerability. An attacker can use ..\/ to bypass the filter rule. Then, this attacker can exploit this vulnerability to delete or read any files on the server. It can also be used to determine whether a file exists.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| B2evolution | B2evolution | 6.8.4 |
References
- http://b2evolution.net/downloads/6-8-5Patch, Vendor Advisory
- http://www.securityfocus.com/bid/95700Third Party Advisory, VDB Entry
- https://github.com/b2evolution/b2evolution/commit/e35f7c195d8c1103d2d981a48cda5ab45ecac48aIssue Tracking, Patch, Third Party Advisory
- https://github.com/b2evolution/b2evolution/issues/36Issue Tracking, Patch, Third Party Advisory
- http://b2evolution.net/downloads/6-8-5Patch, Vendor Advisory
- http://www.securityfocus.com/bid/95700Third Party Advisory, VDB Entry
- https://github.com/b2evolution/b2evolution/commit/e35f7c195d8c1103d2d981a48cda5ab45ecac48aIssue Tracking, Patch, Third Party Advisory
- https://github.com/b2evolution/b2evolution/issues/36Issue Tracking, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5539?
The patch for directory traversal (CVE-2017-5480) in b2evolution version 6.8.4-stable has a bypass vulnerability. An attacker can use ..\/ to bypass the filter rule. Then, this attacker can exploit this vulnerability to delete or read any files on the server. It can also be used to determine whether a file exists.
How severe is CVE-2017-5539?
Severity scoring for CVE-2017-5539 is pending analysis. The EPSS model estimates a 4.14% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5539?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-5533A vulnerability in the server content cache of TIBCO JasperR…9.3
- CVE-2017-5534The tibbr user profiles components of tibbr Community, and t…8.8
- CVE-2017-5535The GridServer Broker, GridServer Driver, and GridServer Eng…6.8
- CVE-2017-5536The GridServer Broker, and GridServer Director components of…6.3
- CVE-2017-5537The password reset form in Weblate before 2.10.1 provides di…
- CVE-2017-5538The kbase_dispatch function in arm/t7xx/r5p0/mali_kbase_core…
- CVE-2017-5541Directory traversal vulnerability in template/usererror.miss…
- CVE-2017-5542Cross-site scripting (XSS) vulnerability in template/usererr…
- CVE-2017-5543includes/classes/ia.core.users.php in Subrion CMS 4.0.5 allo…
- CVE-2017-5544An issue was discovered on FiberHome Fengine S5800 switches …5.9
- CVE-2017-5545The main function in plistutil.c in libimobiledevice libplis…
- CVE-2017-5546The freelist-randomization feature in mm/slab.c in the Linux…7.8
Are you affected by CVE-2017-5539?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST