{"answers":{"affected":"2 open source packages ship an affected version, including io.ktor:ktor. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-38180 in the wild and no public exploit code.","fix":"Upgrade io.ktor:ktor to 2.1.0 or later.","what":"CVE-2022-38180 is a medium-severity authentication bypass vulnerability in JetBrains Ktor, published on 12 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-38180 and fix it if it is affected.\n\nWhat it is: CVE-2022-38180 is a medium-severity authentication bypass vulnerability in JetBrains Ktor, published on 12 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-38180 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.ktor:ktor (Maven): affected all versions; fixed in 2.1.0\n- io.ktor:ktor (Maven): affected all versions; fixed in 2.1.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-2022-38180/ (Markdown: https://insights.sbomify.com/CVE-2022-38180/index.md)","id":"CVE-2022-38180","markdown":"https://insights.sbomify.com/CVE-2022-38180/index.md","name":"CVE-2022-38180","record":{"aliases":["GHSA-hccx-cg4v-hrjx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kotlin web framework","requires_auth":"none","summary":"Attackers can bypass authentication in JetBrains Ktor by exploiting a flaw where the wrong authentication provider is selected.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JetBrains","cpe":[{"product":"ktor","vendor":"jetbrains"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases","ecosystems":["Maven"],"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":"JetBrain Ktor before 2.1.0 vulnerable to selection of wrong authentication provider","id":"CVE-2022-38180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Arm Mali GPU Kernel Driver Use-After-Free","id":"CVE-2022-38181"},"packages":[{"ecosystem":"Maven","fixed":["2.1.0"],"introduced":["0"],"last_affected":[],"package":"io.ktor:ktor","purl":null,"source":"GHSA-hccx-cg4v-hrjx"},{"ecosystem":"Maven","fixed":["2.1.0"],"introduced":["0"],"last_affected":[],"package":"io.ktor:ktor","purl":"pkg:maven/io.ktor/ktor","source":"GHSA-hccx-cg4v-hrjx"}],"prev":{"headline":"JetBrains Ktor before 2.1.0 was vulnerable to a Reflect File Download attack","id":"CVE-2022-38179"},"products":["Ktor"],"published":"2022-08-12","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-12736","kev_date_added":null,"published":"2019-10-02"},{"cvss_score":8.7,"headline":"SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value.","id":"CVE-2022-29930","kev_date_added":null,"published":"2022-05-12"},{"cvss_score":8.6,"headline":"XML external entity in Ktor","id":"CVE-2023-45612","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":7.5,"headline":"Path traversal in Ktor","id":"CVE-2022-48476","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2021-43203","kev_date_added":null,"published":"2021-11-09"},{"cvss_score":6.8,"headline":"Security feature bypass in Ktor","id":"CVE-2023-45613","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2020-26129","kev_date_added":null,"published":"2020-11-16"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["JetBrains"]},"summary":"Attackers can bypass authentication in JetBrains Ktor by exploiting a flaw where the wrong authentication provider is selected.","url":"https://insights.sbomify.com/CVE-2022-38180/"}