{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-37146 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-37146 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-37146 is a medium-severity vulnerability in n/a, published on 8 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-37146 and fix it if it is affected.\n\nWhat it is: CVE-2022-37146 is a medium-severity vulnerability in n/a, published on 8 Sep 2022. 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-2022-37146 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2022-37146/ (Markdown: https://insights.sbomify.com/CVE-2022-37146/index.md)","id":"CVE-2022-37146","markdown":"https://insights.sbomify.com/CVE-2022-37146/index.md","name":"CVE-2022-37146","record":{"aliases":["GHSA-2cxw-7c85-pj9p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PlexTrac platform","requires_auth":"none","summary":"Unauthenticated attackers can enumerate valid usernames by analyzing response time differences during login attempts on the PlexTrac platform.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"plextrac","vendor":"plextrac"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","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-203","name":"Observable Discrepancy"}],"description":"The PlexTrac platform prior to version 1.28.0 allows for username enumeration via HTTP response times on invalid login attempts for users configured to use the PlexTrac authentication provider. Login attempts for valid, unlocked users configured to use PlexTrac as their authentication provider take significantly longer than those for invalid users, allowing for valid users to be enumerated by an unauthenticated remote attacker. Note that the lockout policy implemented in Plextrac version 1.17.0 makes it impossible to distinguish between valid, locked user accounts and user accounts that do not exist, but does not prevent valid, unlocked users from being enumerated.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2022-37146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2022-37149"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2022-37145"},"products":["n/a"],"published":"2022-09-08","related":[{"cvss_score":8.9,"headline":"Arbitrary Directory Write via Runbooks Artifact Upload","id":"CVE-2024-11833","kev_date_added":null,"published":"2024-12-13"},{"cvss_score":8.9,"headline":"Arbitrary File Write via PTRAC Import","id":"CVE-2024-11834","kev_date_added":null,"published":"2024-12-13"},{"cvss_score":8.8,"headline":"Security feature bypass in n/a","id":"CVE-2022-37144","kev_date_added":null,"published":"2022-09-08"},{"cvss_score":8.6,"headline":"Insecure YAML Deserialization","id":"CVE-2024-12687","kev_date_added":null,"published":"2024-12-16"},{"cvss_score":8.6,"headline":"Server-side Request Forgery","id":"CVE-2024-11836","kev_date_added":null,"published":"2024-12-13"},{"cvss_score":8.6,"headline":"N1QL Injection","id":"CVE-2024-11837","kev_date_added":null,"published":"2024-12-13"},{"cvss_score":8.6,"headline":"Local File Inclusion","id":"CVE-2024-11838","kev_date_added":null,"published":"2024-12-13"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"Unauthenticated attackers can enumerate valid usernames by analyzing response time differences during login attempts on the PlexTrac platform.","url":"https://insights.sbomify.com/CVE-2022-37146/"}