Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

CVE-2023-31286

MEDIUMFix: serenity-is/Serenity@11b9d26

CVE-2023-31286 is a medium-severity (CVSS 5.3) CWE-209 vulnerability in Serenity.Net.Core. O3 Security confirms whether CVE-2023-31286 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

User account enumeration in Serenity

Also known asGHSA-w7jm-9x4m-8qc3
Published
Apr 27, 2023
Updated
Jul 15, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Real-World Exposure

2 pkgs affected
.NETSerenity.Net.Core.NETSerenity.Net.Web

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetSerenity.Net.Coreall versions6.7.0
.NETNuGetSerenity.Net.Weball versions6.7.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Serenity.Net.Core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Serenity.Net.Core to 6.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-31286 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-31286 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-31286. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2023-31286 in your dependencies?

O3 detects CVE-2023-31286 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.