{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19101 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19101 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19101 is a medium-severity vulnerability in B\u0026R Automation Studio, published on 29 Apr 2020. 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-2019-19101 and fix it if it is affected.\n\nWhat it is: CVE-2019-19101 is a medium-severity vulnerability in B\u0026R Automation Studio, published on 29 Apr 2020. 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-2019-19101 in the wild and no public exploit code.\n\nAffected product: B\u0026R Automation Studio. 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-19101/ (Markdown: https://insights.sbomify.com/CVE-2019-19101/index.md)","id":"CVE-2019-19101","markdown":"https://insights.sbomify.com/CVE-2019-19101/index.md","name":"CVE-2019-19101","record":{"aliases":["GHSA-xfj2-8v99-wp6x"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Industrial automation software","requires_auth":"none","summary":"Incomplete TLS validation in B\u0026R Automation Studio allows unauthenticated attackers to perform man-in-the-middle attacks on the upgrade service.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ABB","cpe":[{"product":"automation_studio","vendor":"br-automation"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"},{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"A missing secure communication definition and an incomplete TLS validation in the upgrade service in B\u0026R Automation Studio versions 4.0.x, 4.1.x, 4.2.x, \u003c 4.3.11SP, \u003c 4.4.9SP, \u003c 4.5.5SP, \u003c 4.6.4 and \u003c 4.7.2 enable unauthenticated users to perform MITM attacks via the B\u0026R upgrade server.","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":"Incomplete communication encryption and validation in B\u0026R Automation Studio upgrade service","id":"CVE-2019-19101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Zip Slip vulnerability in 3rd-Party library in B\u0026R Automation Studio upgrade service","id":"CVE-2019-19102"},"packages":[],"prev":{"headline":"Privilege escalation via B\u0026R Automation Studio upgrade service","id":"CVE-2019-19100"},"products":["Automation Studio"],"published":"2020-04-29","related":[{"cvss_score":8.3,"headline":"B\u0026R products use insufficient communication encryption","id":"CVE-2024-0220","kev_date_added":null,"published":"2024-02-22"},{"cvss_score":8.3,"headline":"RCE in B\u0026R Automation Studio with crafted project files","id":"CVE-2021-22282","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":8.2,"headline":"Automation Studio and PVI Multiple incorrect permission assignments for services","id":"CVE-2020-24681","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":7.5,"headline":"Privilege escalation via B\u0026R Automation Studio upgrade service","id":"CVE-2019-19100","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":7.2,"headline":"DLL Hijacking Vulnerability in Automation Studio","id":"CVE-2021-22280","kev_date_added":null,"published":"2024-05-14"},{"cvss_score":6.3,"headline":"Zip Slip Vulnerability in B\u0026R Automation Studio Project Import","id":"CVE-2021-22281","kev_date_added":null,"published":"2024-02-02"}],"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":["B\u0026R"]},"summary":"Incomplete TLS validation in B\u0026R Automation Studio allows unauthenticated attackers to perform man-in-the-middle attacks on the upgrade service.","url":"https://insights.sbomify.com/CVE-2019-19101/"}