# CVE-2023-27974: Security feature bypass in n/a

> Bitwarden may auto-fill credentials on subdomains if enabled, potentially exposing passwords to malicious subdomains.

- **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:** No
- **Published:** 8 Mar 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-76q7-gm7v-vj5q

## What is CVE-2023-27974?

CVE-2023-27974 is a high-severity vulnerability in n/a, published on 8 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bitwarden through 2023.2.1 offers password auto-fill when the second-level domain matches, e.g., a password stored for an example.com hosting provider when customer-website.example.com is visited. NOTE: the vendor's position is that "Auto-fill on page load" is not enabled by default.

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

It affects 1 product.


Products: Bitwarden Bitwarden.

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

No fix has been published for CVE-2023-27974 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-27974 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27974 exists.

## Other vulnerabilities in n/a

- [CVE-2018-25081](https://insights.sbomify.com/CVE-2018-25081/): Information disclosure in n/a (high 7.5)
- [CVE-2023-27706](https://insights.sbomify.com/CVE-2023-27706/): Information disclosure in n/a (high 7.1)
- [CVE-2023-38840](https://insights.sbomify.com/CVE-2023-38840/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27974 is a high-severity vulnerability in n/a, published on 8 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27974 exists.

Affected product: n/a. 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-27974/ (Markdown: https://insights.sbomify.com/CVE-2023-27974/index.md)
```

## Sources

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

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