{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-12037 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-12037 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-12037 is a high-severity vulnerability in Baxter PrismaFlex and PrisMax, published on 29 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-12037 and fix it if it is affected.\n\nWhat it is: CVE-2020-12037 is a high-severity vulnerability in Baxter PrismaFlex and PrisMax, published on 29 Jun 2020. 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-2020-12037 in the wild and no public exploit code.\n\nAffected product: Baxter PrismaFlex and PrisMax. 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-2020-12037/ (Markdown: https://insights.sbomify.com/CVE-2020-12037/index.md)","id":"CVE-2020-12037","markdown":"https://insights.sbomify.com/CVE-2020-12037/index.md","name":"CVE-2020-12037","record":{"aliases":["GHSA-crq7-9m4m-xx27"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Medical infusion pump","requires_auth":"none","summary":"Baxter PrismaFlex and PrisMax devices fail to encrypt data in transit, allowing attackers to intercept sensitive patient treatment information.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"prismaflex_firmware","vendor":"baxter"},{"product":"prismax_firmware","vendor":"baxter"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-259","name":"Use of Hard-coded Password"}],"description":"Baxter PrismaFlex all versions, PrisMax all versions prior to 3.x, The affected devices do not implement data-in-transit encryption (e.g., TLS/SSL) when configured to send treatment data to a PDMS (Patient Data Management System) or an EMR (Electronic Medical Record) system. An attacker could observe sensitive data sent from the device.","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":"Weak cryptography in Baxter PrismaFlex and PrisMax","id":"CVE-2020-12037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in EDS Subsystem, FactoryTalk Linx software (Previously called RSLinx Enterprise), RSLinx Classic, RSNetWorx software, Studio 5000 Logix Designer software","id":"CVE-2020-12038"},"packages":[],"prev":{"headline":"Weak cryptography in Baxter PrismaFlex and PrisMax","id":"CVE-2020-12036"},"products":["Baxter PrismaFlex and PrisMax"],"published":"2020-06-29","related":[{"cvss_score":7.5,"headline":"Weak cryptography in Baxter PrismaFlex and PrisMax","id":"CVE-2020-12036","kev_date_added":null,"published":"2020-06-29"},{"cvss_score":4.9,"headline":"Hardcoded credentials in Baxter PrismaFlex and PrisMax","id":"CVE-2020-12035","kev_date_added":null,"published":"2020-06-29"}],"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-04","vendors":["n/a"]},"summary":"Baxter PrismaFlex and PrisMax devices fail to encrypt data in transit, allowing attackers to intercept sensitive patient treatment information.","url":"https://insights.sbomify.com/CVE-2020-12037/"}