CVE-2022-1949· NVD / CVE Program· CNA redhat

An access control bypass vulnerability found in 389-ds-base.

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 74.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: 389-ds-base (Debian:12) 2.3.1-1; 389-ds (openSUSE:Leap 15.3) 1.4.4.19~git38.9951c1101-150300.3.17.1; 389-ds (openSUSE:Leap 15.4) 2.0.15~git26.1ea6a6803-150400.3.5.1.

Low priority for now. Upgrade to 389-ds-base (Debian:12) 2.3.1-1; 389-ds (openSUSE:Leap 15.3) 1.4.4.19~git38.9951c1101-150300.3.17.1; 389-ds (openSUSE:Leap 15.4) 2.0.15~git26.1ea6a6803-150400.3.5.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An access control bypass vulnerability found in 389-ds-base. That mishandling of the filter that would yield incorrect results, but as that has progressed, can be determined that it actually is an access control bypass. This may allow any remote unauthenticated user to issue a filter that allows searching for database items they do not have access to, including but not limited to potentially userPassword hashes and other sensitive data.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Jun 2, 2022
Updated: Jun 17, 2026
EPSS: 1.5% · 74th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
redhat	389 directory server	cpe:2.3:o:redhat:389_directory_server
redhat	directory server	cpe:2.3:a:redhat:directory_server
redhat	enterprise linux	cpe:2.3:o:redhat:enterprise_linux
fedoraproject	fedora	cpe:2.3:o:fedoraproject:fedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

fedoraproject fedora34
fedoraproject fedora35
fedoraproject fedora36
redhat 389 directory server1.3.0.0 and later · up to 2.0.0 inclusive
redhat directory server11.0
redhat directory server12.0
redhat enterprise linux8.0
redhat enterprise linux9.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

n/a 389-ds-base
- 389-ds-base-2.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	389-ds-base	before 2.3.1-1	2.3.1-1
openSUSE:Leap 15.3	389-ds	before 1.4.4.19~git38.9951c1101-150300.3.17.1	1.4.4.19~git38.9951c1101-150300.3.17.1
openSUSE:Leap 15.4	389-ds	before 2.0.15~git26.1ea6a6803-150400.3.5.1	2.0.15~git26.1ea6a6803-150400.3.5.1
openSUSE:Tumbleweed	389-ds	before 2.1.1~git22.faef73366-1.1	2.1.1~git22.faef73366-1.1
SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS	389-ds	before 1.4.2.16~git68.efa843752-150100.7.34.1	1.4.2.16~git68.efa843752-150100.7.34.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS	389-ds	before 1.4.3.30~git2.ca761af4b-150200.3.29.1	1.4.3.30~git2.ca761af4b-150200.3.29.1
SUSE:Linux Enterprise High Performance Computing 15-ESPOS	389-ds	before 1.4.0.31~git15.8b9843b0b-150000.4.27.1	1.4.0.31~git15.8b9843b0b-150000.4.27.1
SUSE:Linux Enterprise Module for Server Applications 15 SP3	389-ds	before 1.4.4.19~git38.9951c1101-150300.3.17.1	1.4.4.19~git38.9951c1101-150300.3.17.1
SUSE:Linux Enterprise Module for Server Applications 15 SP4	389-ds	before 2.0.15~git26.1ea6a6803-150400.3.5.1	2.0.15~git26.1ea6a6803-150400.3.5.1

Same product

redhat: all records

Other highest-scoring records for the same primary product.

CVE-2018-10935A flaw was found in the 389 Directory Server that allows users to cause a crash in the LDAP server using ldapsearch with server side sort.
27Monitor
CVE-2022-0996A vulnerability was found in the 389 Directory Server that allows expired passwords to access the database to cause improper authentication.
26Monitor
CVE-2021-3514When using a sync_repl client in 389-ds-base, an authenticated attacker can cause a NULL pointer dereference using a specially crafted query
26Monitor

Published before and after this one in the same product

← EarlierCVE-2020-35518Mar 26, 2021 · When binding against a DN during authentication, the reply from 389-ds-base will be different whether the DN exists or not.
21Monitor
Later →CVE-2024-1062Feb 12, 2024 · 389-ds-base: a heap overflow leading to denail-of-servce while writing a value larger than 256 chars (in log_entry_attr)
22Monitor
Later →CVE-2026-11793Jun 9, 2026 · 389-ds-base: 389-ds-base: stack buffer overflow in checkprefix() algorithm id parsing
19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:389-ds-base	2.3.1-1 · Debian:12	Package registry (OSV)
opensuse:389-ds	1.4.4.19~git38.9951c1101-150300.3.17.1 · openSUSE:Leap 15.3	Package registry (OSV)
suse:389-ds	1.4.4.19~git38.9951c1101-150300.3.17.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

bugzilla.redhat.com/show_bug.cgi?id=2091781

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records