{"answers":{"affected":"4 open source packages ship an affected version, including Serenity.Net.Core and Serenity.Net.Web. It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31286 exists.","fix":"Upgrade Serenity.Net.Core to 6.7.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-31286 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31286 exists.\n\nAffected packages and fixed versions:\n- Serenity.Net.Core (NuGet): affected all versions; fixed in 6.7.0\n- Serenity.Net.Core (NuGet): affected all versions; fixed in 6.7.0\n- Serenity.Net.Web (NuGet): affected all versions; fixed in 6.7.0\n- Serenity.Net.Web (NuGet): affected all versions; fixed in 6.7.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-31286/ (Markdown: https://insights.sbomify.com/CVE-2023-31286/index.md)","id":"CVE-2023-31286","markdown":"https://insights.sbomify.com/CVE-2023-31286/index.md","name":"CVE-2023-31286","record":{"aliases":["GHSA-w7jm-9x4m-8qc3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Serenity Serene","requires_auth":"none","summary":"Attackers can enumerate valid users via password reset error messages, exposing user existence information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"serene","vendor":"serenity"},{"product":"startsharp","vendor":"serenity"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"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.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"User account enumeration in Serenity","id":"CVE-2023-31286","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":4,"n_references":3,"next":{"headline":"Insufficient token expiration in Serenity","id":"CVE-2023-31287"},"packages":[{"ecosystem":"NuGet","fixed":["6.7.0"],"introduced":["0"],"last_affected":[],"package":"Serenity.Net.Core","purl":null,"source":"GHSA-w7jm-9x4m-8qc3"},{"ecosystem":"NuGet","fixed":["6.7.0"],"introduced":["0"],"last_affected":[],"package":"Serenity.Net.Core","purl":"pkg:nuget/Serenity.Net.Core","source":"GHSA-w7jm-9x4m-8qc3"},{"ecosystem":"NuGet","fixed":["6.7.0"],"introduced":["0"],"last_affected":[],"package":"Serenity.Net.Web","purl":null,"source":"GHSA-w7jm-9x4m-8qc3"},{"ecosystem":"NuGet","fixed":["6.7.0"],"introduced":["0"],"last_affected":[],"package":"Serenity.Net.Web","purl":"pkg:nuget/Serenity.Net.Web","source":"GHSA-w7jm-9x4m-8qc3"}],"prev":{"headline":"Cross Site Scripting (XSS) in Serenity","id":"CVE-2023-31285"},"products":["n/a"],"published":"2023-04-27","related":[{"cvss_score":7.8,"headline":"Insufficient token expiration in Serenity","id":"CVE-2023-31287","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":6.1,"headline":"Cross Site Scripting (XSS) in Serenity","id":"CVE-2023-31285","kev_date_added":null,"published":"2023-04-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["n/a"]},"summary":"Attackers can enumerate valid users via password reset error messages, exposing user existence information.","url":"https://insights.sbomify.com/CVE-2023-31286/"}