{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19389 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19389 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19389 is a medium-severity vulnerability in n/a, published on 26 Dec 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-19389 and fix it if it is affected.\n\nWhat it is: CVE-2019-19389 is a medium-severity vulnerability in n/a, published on 26 Dec 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-19389 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-2019-19389/ (Markdown: https://insights.sbomify.com/CVE-2019-19389/index.md)","id":"CVE-2019-19389","markdown":"https://insights.sbomify.com/CVE-2019-19389/index.md","name":"CVE-2019-19389","record":{"aliases":["GHSA-rm67-h645-8jg2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Kotlin web framework","requires_auth":"low_privilege","summary":"Attackers can inject headers into HTTP responses via the Ktor framework, potentially leading to cache poisoning or XSS.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ktor","vendor":"jetbrains"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"JetBrains Ktor framework before version 1.2.6 was vulnerable to HTTP Response Splitting.","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 Neutralization of Input During Web Page Generation (Cross-site Scripting) in Ktor","id":"CVE-2019-19389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19390"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19388"},"products":["n/a"],"published":"2019-12-26","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":"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-05","vendors":["n/a"]},"summary":"Attackers can inject headers into HTTP responses via the Ktor framework, potentially leading to cache poisoning or XSS.","url":"https://insights.sbomify.com/CVE-2019-19389/"}