CWE
200
Advisory Published
Updated

GHSA-fpq5-4vwm-78x4

First published: Fri Nov 17 2023(Updated: )

### Summary This vulnerability occurs when application is not checking access of each type of users as per their role and it autorizing the users to access any feature. When user access his Device dashboard in librenms, one request is going to graph.php to access image of graphs generated on the particular Device. This request can be accessed by lower privileged users as well and they can enumerate devices on librenms with their id or hostname. ### Details _Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._ ### PoC 1. Login with Lower privilege user 2. Go to /graph.php?width=150&height=45&device=1&type=device_ping_perf&from=1699022192&legend=no&bg=FFFFFF00&popup_title=ICMP+Response 3. If its showing image with "device*ping_perf" which confirms that there is device with id 1 4. Now you can change device parameter in above URL with hostname to check if that Hostname/IP exist or not like http://127.0.0.1:8000/graph.php?width=150&height=45&device=127.0.0.1&type=device_ping_perf&from=1699022192&legend=no&bg=FFFFFF00&popup_title=ICMP+Response 5. If device hostname doesn't exist then it should show 500 error Check attached screenshots for more info Vulnerable code: https://github.com/librenms/librenms/blob/fa93034edd40c130c2ff00667ca2498d84be6e69/html/graph.php#L19C1-L25C2 Above is vulnerable line of code from Line number 19-25 This is not checking privilege of users to access any device hostname, its just checking if user is authenticated or not ### Impact Low privilege users can see all devices registered by admin users by using this method ### Solution Implement privilege access control feature to check if low privilege user have access or not. ### Screenshots:- <img width="967" alt="Screenshot 2023-11-04 at 8 31 15 PM" src="https://user-images.githubusercontent.com/31764504/281085588-1c5d81b9-83d7-4ba8-baf3-03c95a99cefe.png"> <img width="973" alt="Screenshot 2023-11-04 at 8 31 36 PM" src="https://user-images.githubusercontent.com/31764504/281085614-7a4d13b0-d316-4d24-bdd2-05c3a80ffd59.png"> <img width="955" alt="Screenshot 2023-11-04 at 8 31 48 PM" src="https://user-images.githubusercontent.com/31764504/281085629-43aa2b6f-7b18-415f-8001-519bda45f918.png">

Affected SoftwareAffected VersionHow to fix
composer/librenms/librenms<23.11.0
23.11.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of GHSA-fpq5-4vwm-78x4?

    The severity of GHSA-fpq5-4vwm-78x4 is medium with a severity value of 4.3.

  • How does GHSA-fpq5-4vwm-78x4 vulnerability occur?

    GHSA-fpq5-4vwm-78x4 vulnerability occurs when the application does not check the access of each type of user as per their role, allowing unauthorized access to features.

  • Which software is affected by GHSA-fpq5-4vwm-78x4?

    The software affected by GHSA-fpq5-4vwm-78x4 is librenms version 23.11.0.

  • How can I fix GHSA-fpq5-4vwm-78x4 vulnerability?

    To fix GHSA-fpq5-4vwm-78x4 vulnerability, update the librenms software to version 23.11.0 or later.

  • What is the CWE ID of GHSA-fpq5-4vwm-78x4?

    The CWE ID of GHSA-fpq5-4vwm-78x4 is 200.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203