CVE-2017-18123
UnknownEPSS 2.65%
Last modified
CVE-2017-18123 is a vulnerability of currently unknown severity. The call parameter of /lib/exe/ajax.php in DokuWiki through 2017-02-19e does not properly encode user input, which leads to a reflected file download vulnerability, and allows remote attackers to run arbitrary programs.. EPSS estimates a 2.65% chance of exploitation in the next 30 days.
Description
The call parameter of /lib/exe/ajax.php in DokuWiki through 2017-02-19e does not properly encode user input, which leads to a reflected file download vulnerability, and allows remote attackers to run arbitrary programs.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Dokuwiki | Dokuwiki | <= 2017-02-19e |
| Debian | Debian Linux | 7.0 |
References
- https://github.com/splitbrain/dokuwiki/issues/2029Exploit, Issue Tracking, Third Party Advisory
- https://github.com/splitbrain/dokuwiki/pull/2019Issue Tracking
- https://hackerone.com/reports/238316Permissions Required
- https://lists.debian.org/debian-lts-announce/2018/02/msg00004.htmlIssue Tracking, Mailing List, Third Party Advisory
- https://vulnhive.com/2018/000004Exploit, Issue Tracking, Patch, Third Party Advisory
- https://github.com/splitbrain/dokuwiki/issues/2029Exploit, Issue Tracking, Third Party Advisory
- https://github.com/splitbrain/dokuwiki/pull/2019Issue Tracking
- https://hackerone.com/reports/238316Permissions Required
- https://lists.debian.org/debian-lts-announce/2018/02/msg00004.htmlIssue Tracking, Mailing List, Third Party Advisory
- https://vulnhive.com/2018/000004Exploit, Issue Tracking, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-18123?
The call parameter of /lib/exe/ajax.php in DokuWiki through 2017-02-19e does not properly encode user input, which leads to a reflected file download vulnerability, and allows remote attackers to run arbitrary programs.
How severe is CVE-2017-18123?
Severity scoring for CVE-2017-18123 is pending analysis. The EPSS model estimates a 2.65% probability of exploitation in the next 30 days.
How do I fix CVE-2017-18123?
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-18112Affected versions of Atlassian Fisheye allow remote attacker…6.5
- CVE-2017-18113The DefaultOSWorkflowConfigurator class in Jira Server and J…8.8
- CVE-2017-1812Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-18120A double-free bug in the read_gif function in gifread.c in g…
- CVE-2017-18121The consentAdmin module in SimpleSAMLphp through 1.14.15 is …
- CVE-2017-18122A signature-validation bypass issue was discovered in Simple…
- CVE-2017-18124During secure boot, addition is performed on uint8 ptrs whic…
- CVE-2017-18125In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18126In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18127In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18128In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18129In Android before security patch level 2018-04-05 on Qualcom…
Are you affected by CVE-2017-18123?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST