Описание
thorsten/phpmyfaq Unintended File Download Triggered by Embedded Frames
Summary
A vulnerability exists in the FAQ Record component where a privileged attacker can trigger a file download on a victim's machine upon page visit by embedding it in an element without user interaction or explicit consent.
Details
In http://localhost/admin/index.php?action=editentry&id=20&lang=en, where a FAQ record is either created or edited, an attacker can insert an iframe, as "source code", pointing to a prior "malicious" attachment that the attacker has uploaded via FAQ "new attachment" upload, such that any page visits to this FAQ will trigger an automated download (from the edit screen, download is automated; from the faq page view as a normal user, depending on the browser, a pop up confirmation may be presented before the actual download. Firebox browser, for instance, does not require any interactions).
PoC
-
create a new FAQ record and upload a "malicious" file - in my case, I uploaded an eicar file. take note of the uri, ie
<iframe "index.php?action=attachment&id=2"
-
in the FAQ record, insert a "source code" blob using the "< >" button
-
insert in the following snippet:
and save FAQ record -
once the edit page reloads, the malicious code will be downloaded onto the local machine without user interaction:
(uploaded a POC for easy demonstration: https://roy.demo.phpmyfaq.de/admin/index.php?action=editentry&id=20&lang=en although a fresh installation overwrites this demo instance every 24 hours)
(as a logged in normal user, visit: https://roy.demo.phpmyfaq.de/content/1/20/en/20.html)
Impact
Malicious code or binaries could be dropped on visitors' machines when visiting the FAQ platform. Take a worm or ransomware for instance.
Пакеты
thorsten/phpmyfaq
< 3.2.10
3.2.10
Связанные уязвимости
phpMyFAQ is an open source FAQ web application. Prior to version 3.2.10, a vulnerability exists in the FAQ Record component where a privileged attacker can trigger a file download on a victim's machine upon page visit by embedding it in an <iframe> element without user interaction or explicit consent. Version 3.2.10 fixes the issue.