# CVE-2021-28374: Information disclosure in n/a

> Weak permissions on the authdaemon directory allow attackers to read sensitive user information, including potential cleartext passwords.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-28374, DLA-2625-1, GHSA-hcm8-3cv3-g73f, UBUNTU-CVE-2021-28374

## What is CVE-2021-28374?

CVE-2021-28374 is a high-severity vulnerability in Debian Debian Linux, published on 15 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Debian courier-authlib package before 0.71.1-2 for Courier Authentication Library creates a /run/courier/authdaemon directory with weak permissions, allowing an attacker to read user information. This may include a cleartext password in some configurations. In general, it includes the user's existence, uid and gids, home and/or Maildir directory, quota, and some type of password information (such as a hash).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2021-28374?

It affects 2 products.


Products: Debian Courier-Authlib, Debian Debian Linux.

## How do I fix CVE-2021-28374?

Upgrade to a fixed version.

## Is CVE-2021-28374 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28374 and fix it if it is affected.

What it is: CVE-2021-28374 is a high-severity vulnerability in Debian Debian Linux, published on 15 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-28374 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2021-28374/ (Markdown: https://insights.sbomify.com/CVE-2021-28374/index.md)
```

## Sources

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

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