# CVE-2023-1055: Information disclosure in Red Hat Directory Server

> Local attackers can view hashed passwords by listing processes due to incorrect attribute decoding in Red Hat Directory Server.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2023
- **Updated:** 11 Mar 2025
- **Also known as:** DEBIAN-CVE-2023-1055, GHSA-w8wv-xqxw-7vgx, RHSA-2023:3489, RHSA-2023:4655, UBUNTU-CVE-2023-1055

## What is CVE-2023-1055?

CVE-2023-1055 is a medium-severity vulnerability in Fedoraproject Fedora, published on 27 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in RHDS 11 and RHDS 12. While browsing entries LDAP tries to decode the userPassword attribute instead of the userCertificate attribute which could lead into sensitive information leaked. An attacker with a local account where the cockpit-389-ds is running can list the processes and display the hashed passwords. The highest threat from this vulnerability is to data confidentiality.

Weakness: CWE-295 (Improper Certificate Validation), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-1055?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `389-ds-base` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-debuginfo` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-debugsource` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-devel` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-legacy-tools` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-legacy-tools-debuginfo` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-libs` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-libs-debuginfo` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-snmp` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base-snmp-debuginfo` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `cockpit-389-ds` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `python3-lib389` | Red Hat:directory_server:11.6::el8 | All versions | 0:1.4.3.34-1.module+el8dsrv+18380+8350b80e |
| `389-ds-base` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `389-ds-base-debuginfo` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `389-ds-base-debugsource` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `389-ds-base-devel` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `389-ds-base-libs` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `389-ds-base-libs-debuginfo` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `389-ds-base-snmp` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `389-ds-base-snmp-debuginfo` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `cockpit-389-ds` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |
| `python3-lib389` | Red Hat:directory_server:12.1::el9 | All versions | 0:2.1.8-1.module+el9dsrv+18377+a10e6f72 |

Products: Fedoraproject Fedora, Redhat Directory Server.

## How do I fix CVE-2023-1055?

Apply the vendor's patch.

## Is CVE-2023-1055 being exploited?

There is no known exploitation of CVE-2023-1055 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1055 and fix it if it is affected.

What it is: CVE-2023-1055 is a medium-severity vulnerability in Fedoraproject Fedora, published on 27 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1055 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-1055/ (Markdown: https://insights.sbomify.com/CVE-2023-1055/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1055
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1055
- OSV: https://osv.dev/vulnerability/CVE-2023-1055

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-1055/
Summaries are generated and may contain mistakes; the official description above is the record.
