CVE-2022-0587 json
Improper Authorization in librenms/librenms
published 4y ago modified 4mo ago also GHSA-ppfm-rj6p-38q6 , EUVD-2022-1132
- cvss
- 7.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Improper Authorization in Packagist librenms/librenms prior to 22.2.0.
Patch / fix
- packagist librenms/librenms 22.2.0
- librenms librenms/librenms 22.2.0
Is CVE-2022-0587 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/0c7c9ecd-33ac-4865-b05b-447ced735469 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
| GitHub | 3.0 | 7.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | librenms/librenms | <22.2.0 |
22.2.0 |
Affected products
- librenms librenms/librenms
Classification
- Weakness
-
- CWE-285 Improper Authorization
References
-
github.com
/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7
web, patch, third-party-advisory
-
huntr.dev
/bounties/0c7c9ecd-33ac-4865-b05b-447ced735469
web, exploit, third-party-advisory
-
notes.netbytesec.com
/2022/02/multiple-vulnerabilities-in-librenms.html
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-0587
advisory
-
github.com
/librenms/librenms
package
Sources
- CVE List CVE-2022-0587
- GitHub Advisory GHSA-ppfm-rj6p-38q6
- NVD CVE-2022-0587
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.