# CVE-2023-31286: User account enumeration in Serenity

> Attackers can enumerate valid users via password reset error messages, exposing user existence information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 27 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-w7jm-9x4m-8qc3

## What is CVE-2023-31286?

CVE-2023-31286 is a medium-severity vulnerability in n/a, published on 27 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Serenity Serene (and StartSharp) before 6.7.0. When a password reset request occurs, the server response leaks the existence of users. If one tries to reset a password of a non-existent user, an error message indicates that this user does not exist.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

4 open source packages ship an affected version, including Serenity.Net.Core and Serenity.Net.Web. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Serenity.Net.Core` | NuGet | All versions | 6.7.0 |
| `Serenity.Net.Core` | NuGet | All versions | 6.7.0 |
| `Serenity.Net.Web` | NuGet | All versions | 6.7.0 |
| `Serenity.Net.Web` | NuGet | All versions | 6.7.0 |

Products: Serenity Serene, Serenity Startsharp.

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

Upgrade Serenity.Net.Core to 6.7.0 or later.

## Is CVE-2023-31286 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-31287](https://insights.sbomify.com/CVE-2023-31287/): Insufficient token expiration in Serenity (high 7.8)
- [CVE-2023-31285](https://insights.sbomify.com/CVE-2023-31285/): Cross Site Scripting (XSS) in Serenity (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31286 is a medium-severity vulnerability in n/a, published on 27 Apr 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-31286 exists.

Affected packages and fixed versions:
- Serenity.Net.Core (NuGet): affected all versions; fixed in 6.7.0
- Serenity.Net.Core (NuGet): affected all versions; fixed in 6.7.0
- Serenity.Net.Web (NuGet): affected all versions; fixed in 6.7.0
- Serenity.Net.Web (NuGet): affected all versions; fixed in 6.7.0

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-31286/ (Markdown: https://insights.sbomify.com/CVE-2023-31286/index.md)
```

## Sources

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

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