CVE-2023-48294

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

Screenshots:-

Low privilege users can see all devices registered by admin users by using this method

CVE-2023-48294 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (23.11.0); upgrading removes the vulnerable code path.

Kodem intelligence

Implement privilege access control feature to check if low privilege user have access or not.

1. What is CVE-2023-48294? CVE-2023-48294 is a medium-severity security vulnerability in librenms/librenms (composer), affecting versions < 23.11.0. It is fixed in 23.11.0.
2. How severe is CVE-2023-48294? CVE-2023-48294 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of librenms/librenms are affected by CVE-2023-48294? librenms/librenms (composer) versions < 23.11.0 is affected.
4. Is there a fix for CVE-2023-48294? Yes. CVE-2023-48294 is fixed in 23.11.0. Upgrade to this version or later.
5. Is CVE-2023-48294 exploitable, and should I be worried? Whether CVE-2023-48294 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-48294 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-48294? Upgrade librenms/librenms to 23.11.0 or later.