{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-31123 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-31123 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31123 is a critical authentication bypass vulnerability in effectindex tripreporter, published on 8 May 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-31123 and fix it if it is affected.\n\nWhat it is: CVE-2023-31123 is a critical authentication bypass vulnerability in effectindex tripreporter, published on 8 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-31123 in the wild and no public exploit code.\n\nAffected product: effectindex tripreporter. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-31123/ (Markdown: https://insights.sbomify.com/CVE-2023-31123/index.md)","id":"CVE-2023-31123","markdown":"https://insights.sbomify.com/CVE-2023-31123/index.md","name":"CVE-2023-31123","record":{"aliases":["GHSA-356r-rwp8-h6m6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Trip reporting platform","requires_auth":"none","summary":"Attackers can log in as any user by providing a valid password format, leading to account takeover and data exposure in TripReporter instances.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tripreporter","vendor":"effectindex"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"`effectindex/tripreporter` is a community-powered, universal platform for submitting and analyzing trip reports. Prior to commit bd80ba833b9023d39ca22e29874296c8729dd53b, any user with an account on an instance of `effectindex/tripreporter`, e.g. `subjective.report`, may be affected by an improper password verification vulnerability. The vulnerability allows any user with a password matching the password requirements to log in as any user. This allows access to accounts / data loss of the user. This issue is patched in commit bd80ba833b9023d39ca22e29874296c8729dd53b. No action necessary for users of `subjective.report`, and anyone running their own instance should update to this commit or newer as soon as possible. As a workaround, someone running their own instance may apply the patch manually.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"effectindex/tripreporter vulnerable to improper password verification on POST `/api/v1/account/login`","id":"CVE-2023-31123","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"AutoTools does not set CARES_RANDOM_FILE during cross compilation","id":"CVE-2023-31124"},"packages":[],"prev":{"headline":"Apache HTTP Server: mod_macro buffer over-read","id":"CVE-2023-31122"},"products":["tripreporter"],"published":"2023-05-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-29","vendors":["effectindex"]},"summary":"Attackers can log in as any user by providing a valid password format, leading to account takeover and data exposure in TripReporter instances.","url":"https://insights.sbomify.com/CVE-2023-31123/"}