{"answers":{"affected":"4 open source packages ship an affected version, including Serenity.Net.Core and Serenity.Net.Web. It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-31287 in the wild and no public exploit code.","fix":"Upgrade Serenity.Net.Core to 6.7.0 or later.","what":"CVE-2023-31287 is a high-severity vulnerability in n/a, published on 27 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-31287 and fix it if it is affected.\n\nWhat it is: CVE-2023-31287 is a high-severity vulnerability in n/a, published on 27 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-31287 in the wild and no public exploit code.\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-31287/ (Markdown: https://insights.sbomify.com/CVE-2023-31287/index.md)","id":"CVE-2023-31287","markdown":"https://insights.sbomify.com/CVE-2023-31287/index.md","name":"CVE-2023-31287","record":{"aliases":["GHSA-2hp9-3xfr-r9w2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Serenity Serene","requires_auth":"low_privilege","summary":"Attackers can reuse password reset tokens to take over user accounts if they access browser history, affecting Serenity Serene users.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"serene","vendor":"serenity"},{"product":"startsharp","vendor":"serenity"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"}],"description":"An issue was discovered in Serenity Serene (and StartSharp) before 6.7.0. Password reset links are sent by email. A link contains a token that is used to reset the password. This token remains valid even after the password reset and can be used a second time to change the password of the corresponding user. The token expires only 3 hours after issuance and is sent as a query parameter when resetting. An attacker with access to the browser history can thus use the token again to change the password in order to take over the account.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insufficient token expiration in Serenity","id":"CVE-2023-31287","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"business_logic","year":"2023"},"n_packages":4,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2023-31289"},"packages":[{"ecosystem":"NuGet","fixed":["6.7.0"],"introduced":["0"],"last_affected":[],"package":"Serenity.Net.Core","purl":null,"source":"GHSA-2hp9-3xfr-r9w2"},{"ecosystem":"NuGet","fixed":["6.7.0"],"introduced":["0"],"last_affected":[],"package":"Serenity.Net.Core","purl":"pkg:nuget/Serenity.Net.Core","source":"GHSA-2hp9-3xfr-r9w2"},{"ecosystem":"NuGet","fixed":["6.7.0"],"introduced":["0"],"last_affected":[],"package":"Serenity.Net.Web","purl":null,"source":"GHSA-2hp9-3xfr-r9w2"},{"ecosystem":"NuGet","fixed":["6.7.0"],"introduced":["0"],"last_affected":[],"package":"Serenity.Net.Web","purl":"pkg:nuget/Serenity.Net.Web","source":"GHSA-2hp9-3xfr-r9w2"}],"prev":{"headline":"User account enumeration in Serenity","id":"CVE-2023-31286"},"products":["n/a"],"published":"2023-04-27","related":[{"cvss_score":6.1,"headline":"Cross Site Scripting (XSS) in Serenity","id":"CVE-2023-31285","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":5.3,"headline":"User account enumeration in Serenity","id":"CVE-2023-31286","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["n/a"]},"summary":"Attackers can reuse password reset tokens to take over user accounts if they access browser history, affecting Serenity Serene users.","url":"https://insights.sbomify.com/CVE-2023-31287/"}