{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11774 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11774 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11774 is a high-severity vulnerability in The Eclipse Foundation Eclipse OMR, published on 12 Sep 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-11774 and fix it if it is affected.\n\nWhat it is: CVE-2019-11774 is a high-severity vulnerability in The Eclipse Foundation Eclipse OMR, published on 12 Sep 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-11774 in the wild and no public exploit code.\n\nAffected product: The Eclipse Foundation Eclipse OMR. 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-11774/ (Markdown: https://insights.sbomify.com/CVE-2019-11774/index.md)","id":"CVE-2019-11774","markdown":"https://insights.sbomify.com/CVE-2019-11774/index.md","name":"CVE-2019-11774","record":{"aliases":["GHSA-c4qj-5gg4-8hwf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse OMR library","requires_auth":"none","summary":"A race condition in Eclipse OMR's loop versioner can lead to out-of-bounds array reads, potentially causing crashes or arbitrary code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"omr","vendor":"eclipse"}],"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":"Prior to 0.1, all builds of Eclipse OMR 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":false,"headline":"Race condition in Eclipse OMR","id":"CVE-2019-11774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in Eclipse OpenJ9","id":"CVE-2019-11775"},"packages":[],"prev":{"headline":"Privilege escalation in Eclipse OMR","id":"CVE-2019-11773"},"products":["Eclipse OMR"],"published":"2019-09-12","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Eclipse OMR","id":"CVE-2019-11773","kev_date_added":null,"published":"2019-09-12"},{"cvss_score":7.1,"headline":"Eclipse OMR: Buffer overflow vulnerability","id":"CVE-2025-1471","kev_date_added":null,"published":"2025-02-21"},{"cvss_score":6.9,"headline":"Memory corruption in Eclipse OMR","id":"CVE-2026-1188","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":6.9,"headline":"OMR on Z processors Exposing a possible buffer over-read problem","id":"CVE-2025-14549","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":5.7,"headline":"Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compare is zero","id":"CVE-2026-16243","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":5.1,"headline":"Eclipse OMR: Null pointer dereference vulnerability","id":"CVE-2025-1470","kev_date_added":null,"published":"2025-02-21"}],"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 Eclipse OMR's loop versioner can lead to out-of-bounds array reads, potentially causing crashes or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2019-11774/"}