Skip to content
Fencer Vulns
critical 9.8

CVE-2022-0730 json

Under certain ldap conditions, Cacti authentication can be bypassed with certain credential types.

published 2022-03-03 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-15799

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.5%
EPSS 3.5% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

Under certain ldap conditions, Cacti authentication can be bypassed with certain credential types.

Patch / fix

  • cacti Debian 14, Debian 13, Debian 12 1.2.20+ds1-1

debian advisories DEBIAN-CVE-2022-0730

  • cacti openSUSE Tumbleweed 1.2.20-1.1
  • cacti-spine Package Hub 15 SP3, Package Hub 12, openSUSE Leap 15.3 1.2.20-bp153.2.9.1
  • cacti Package Hub 15 SP3, Package Hub 12, openSUSE Leap 15.3 1.2.20-bp153.2.9.1

opensuse advisories openSUSE-SU-2024:12016-1openSUSE-SU-2022:0145-1

  • cacti Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 1.2.20-r0

alpine advisories ALPINE-CVE-2022-0730

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-0730 updated cvss 8.1

cacti: Authentication bypass under certain LDAP server environments

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.50% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • n/a Cati

Classification

Weakness

References

Sources

Fencer Vulns 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.