GHSA-h3rv-q4rq-pqcv — librenms/librenms
Fix: librenms/librenms#18777GHSA-h3rv-q4rq-pqcv is a SQL Injection vulnerability in librenms/librenms. A fix is available for librenms/librenms — see the affected versions and patch details below.
LibreNMS: SQL Injection in ajax_table.php spreads through a covert data stream.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-h3rv-q4rq-pqcv.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
librenms/librenmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
SQL Injection in IPv6 Address Search functionality via address parameter*
A SQL injection vulnerability exists in the ajax_table.php endpoint. The application fails to properly sanitize or parameterize user input when processing IPv6 address searches. Specifically, the address parameter is split into an address and a prefix, and the prefix portion is directly concatenated into the SQL query string without validation. This allows an attacker to inject arbitrary SQL commands, potentially leading to unauthorized data access or database manipulation.
Details
The vulnerability is located in the logic that handles address searching when search_type is set to ipv6.
The application takes the user-supplied address parameter and splits it using the / delimiter:
[$address, $prefix] = explode('/', $vars['address']);
If the search_type is ipv6 and the $prefix variable is not empty, the code constructs the SQL query by directly concatenating the $prefix variable into the string:
} elseif ($vars['search_type'] == 'ipv6') {
// ... code omitted ...
if (! empty($prefix)) {
// VULNERABILITY: Direct concatenation of user input
$sql .= " AND ipv6_prefixlen = '$prefix'";
}
}
Unlike the ipv4 block, which attempts to use prepared statements (binding parameters via $param[]), the ipv6 block treats the prefix as a raw string. By supplying an input containing a /, an attacker can populate the $prefix variable. If this variable contains single quotes ('), it breaks out of the string literal in the SQL statement, enabling SQL injection.
Vulnerable Code Snippet:
if (! empty($prefix)) {
$sql .= " AND ipv6_prefixlen = '$prefix'";
}
PoC
To reproduce this vulnerability, an attacker can send a specially crafted HTTP POST request to the ajax_table.php endpoint.
Payload breakdown:
-
search_type=ipv6: Forces the execution flow into the vulnerable elseif block.
-
address=snow/1nd'":
-
The explode function splits this into $address = 'snow' and $prefix = "1nd'"".
-
The SQL query becomes: ... AND ipv6_prefixlen = '1nd'"'.
-
The single quote ' closes the string definition in the SQL query, and the subsequent characters allow for SQL syntax manipulation.
-
Reproduction Steps:
-
Access the application instance.
-
Send the following request (adjusting the host as necessary):
POST /ajax_table.php HTTP/1.1
Host: localhost
id=address-search&search_type=ipv6&address=snow/1nd'"
Impact
This vulnerability allows an attacker to execute arbitrary SQL queries against the database.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | librenms/librenms | all versions | 26.2.0composer require librenms/librenms:^26.2.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for librenms/librenms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update librenms/librenms to 26.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h3rv-q4rq-pqcv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h3rv-q4rq-pqcv can be triaged on real exposure rather than presence alone.
Tailored to GHSA-h3rv-q4rq-pqcv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-h3rv-q4rq-pqcv in your dependencies?
O3 Security finds GHSA-h3rv-q4rq-pqcv across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.