{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2019-11775 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-11775 is a high-severity vulnerability in Redhat Enterprise Linux Desktop, published on 30 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-11775 and fix it if it is affected.\n\nWhat it is: CVE-2019-11775 is a high-severity vulnerability in Redhat Enterprise Linux Desktop, published on 30 Jul 2019. 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-2019-11775 in the wild and no public exploit code.\n\nAffected product: Redhat Enterprise Linux Desktop. 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-11775/ (Markdown: https://insights.sbomify.com/CVE-2019-11775/index.md)","id":"CVE-2019-11775","markdown":"https://insights.sbomify.com/CVE-2019-11775/index.md","name":"CVE-2019-11775","record":{"aliases":["GHSA-3x93-p299-w98q"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Java JIT compiler","requires_auth":"none","summary":"A race condition in the Eclipse OpenJ9 JIT compiler can lead to out-of-bounds array reads, potentially allowing code execution or denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"openj9","vendor":"eclipse"},{"product":"enterprise_linux_desktop","vendor":"redhat"},{"product":"enterprise_linux_server","vendor":"redhat"},{"product":"enterprise_linux_workstation","vendor":"redhat"},{"product":"satellite","vendor":"redhat"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"All builds of Eclipse OpenJ9 prior to 0.15 contain a bug where the loop versioner may fail to privatize a value that is pulled out of the loop by versioning - for example if there is a condition that is moved out of the loop that reads a field we may not privatize the value of that field in the modified copy of the loop allowing the test to see one value of the field and subsequently the loop to see a modified field value without retesting the condition moved out of the loop. This can lead to a variety of different issues but read out of array bounds is one major consequence of these problems.","ecosystems":[],"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":"Race condition in Eclipse OpenJ9","id":"CVE-2019-11775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:enterprise_linux_desktop","products":["redhat:enterprise_linux_desktop","redhat:enterprise_linux_server","redhat:enterprise_linux_workstation","redhat:satellite"],"type":"race_condition","year":"2019"},"n_packages":0,"n_references":7,"next":{"headline":"Cross-site scripting in Eclipse BIRT","id":"CVE-2019-11776"},"packages":[],"prev":{"headline":"Race condition in Eclipse OMR","id":"CVE-2019-11774"},"products":["Eclipse OpenJ9"],"published":"2019-07-30","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Eclipse OMR","id":"CVE-2021-41035","kev_date_added":null,"published":"2021-10-25"},{"cvss_score":9.8,"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2020-27221","kev_date_added":null,"published":"2021-01-21"},{"cvss_score":9.8,"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2019-11772","kev_date_added":null,"published":"2019-07-17"},{"cvss_score":9.8,"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2018-12547","kev_date_added":null,"published":"2019-02-11"},{"cvss_score":9.8,"headline":"Null dereference in Eclipse OpenJ9","id":"CVE-2018-12549","kev_date_added":null,"published":"2019-02-11"},{"cvss_score":9.8,"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2018-12548","kev_date_added":null,"published":"2019-01-31"},{"cvss_score":9.1,"headline":"Missing authorization in Eclipse OpenJ9","id":"CVE-2019-17631","kev_date_added":null,"published":"2019-10-17"}],"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":["The Eclipse Foundation"]},"summary":"A race condition in the Eclipse OpenJ9 JIT compiler can lead to out-of-bounds array reads, potentially allowing code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2019-11775/"}