{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11690 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2019-11690 is a medium-severity vulnerability in n/a, published on 3 May 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-11690 and fix it if it is affected.\n\nWhat it is: CVE-2019-11690 is a medium-severity vulnerability in n/a, published on 3 May 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-11690 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-11690/ (Markdown: https://insights.sbomify.com/CVE-2019-11690/index.md)","id":"CVE-2019-11690","markdown":"https://insights.sbomify.com/CVE-2019-11690/index.md","name":"CVE-2019-11690","record":{"aliases":["DEBIAN-CVE-2019-11690","GHSA-6xpg-gw5j-9x8w","UBUNTU-CVE-2019-11690"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"U-Boot bootloader","requires_auth":"none","summary":"Attackers can predict UUIDs in U-Boot when random UUID support is enabled, potentially bypassing security checks relying on these values.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"u-boot","vendor":"denx"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"gen_rand_uuid in lib/uuid.c in Das U-Boot v2014.04 through v2019.04 lacks an srand call, which allows attackers to determine UUID values in scenarios where CONFIG_RANDOM_UUID is enabled, and Das U-Boot is relied upon for UUID values of a GUID Partition Table of a boot 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":true,"headline":"Weak cryptography in n/a","id":"CVE-2019-11690","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":"Use after free in Firefox","id":"CVE-2019-11691"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-11689"},"products":["n/a"],"published":"2019-05-03","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2022-34835","kev_date_added":null,"published":"2022-06-29"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-30767","kev_date_added":null,"published":"2022-05-16"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2020-8432","kev_date_added":null,"published":"2020-01-29"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-14192","kev_date_added":null,"published":"2019-07-31"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14193","kev_date_added":null,"published":"2019-07-31"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14194","kev_date_added":null,"published":"2019-07-31"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14195","kev_date_added":null,"published":"2019-07-31"}],"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":"Attackers can predict UUIDs in U-Boot when random UUID support is enabled, potentially bypassing security checks relying on these values.","url":"https://insights.sbomify.com/CVE-2019-11690/"}