{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-39238 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-39238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39238 is a medium-severity authentication bypass vulnerability in arvados, published on 23 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-39238 and fix it if it is affected.\n\nWhat it is: CVE-2022-39238 is a medium-severity authentication bypass vulnerability in arvados, published on 23 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-39238 in the wild and no public exploit code.\n\nAffected product: arvados. 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-39238/ (Markdown: https://insights.sbomify.com/CVE-2022-39238/index.md)","id":"CVE-2022-39238","markdown":"https://insights.sbomify.com/CVE-2022-39238/index.md","name":"CVE-2022-39238","record":{"aliases":["GHSA-87jr-xwhg-cxjv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Arvados platform","requires_auth":"low_privilege","summary":"Attackers can bypass authentication in Arvados when using PAM, gaining access with disabled or expired accounts.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"arvados","vendor":"arvados"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Arvados is an open source platform for managing and analyzing biomedical big data. In versions prior to 2.4.3, when using Portable Authentication Modules (PAM) for user authentication, if a user presented valid credentials but the account is disabled or otherwise not allowed to access the host (such as an expired password), it would still be accepted for access to Arvados. Other authentication methods (LDAP, OpenID Connect) supported by Arvados are not affected by this flaw. This issue is patched in version 2.4.3. Workaround for this issue is to migrate to a different authentication method supported by Arvados, such as LDAP.","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":"Improper Authentication in Arvados when using PAM as identity provider","id":"CVE-2022-39238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"@netlify/ipx vulnerable to Full Response SSRF and Stored XSS via Cache Poisoning and Improper Host Validation","id":"CVE-2022-39239"},"packages":[],"prev":{"headline":"Digital Signature Hash Algorithms Not Validated in sylabs/sif","id":"CVE-2022-39237"},"products":["arvados"],"published":"2022-09-23","related":[{"cvss_score":7.9,"headline":"Authenticated remote code execution due to insecure deserialization (GHSL-2022-063)","id":"CVE-2022-36006","kev_date_added":null,"published":"2022-08-14"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["arvados"]},"summary":"Attackers can bypass authentication in Arvados when using PAM, gaining access with disabled or expired accounts.","url":"https://insights.sbomify.com/CVE-2022-39238/"}