{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1549 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-1549 is a medium-severity vulnerability in Openssl Openssl, published on 10 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-1549 and fix it if it is affected.\n\nWhat it is: CVE-2019-1549 is a medium-severity vulnerability in Openssl Openssl, published on 10 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-1549 in the wild and no public exploit code.\n\nAffected product: Openssl Openssl. 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-1549/ (Markdown: https://insights.sbomify.com/CVE-2019-1549/index.md)","id":"CVE-2019-1549","markdown":"https://insights.sbomify.com/CVE-2019-1549/index.md","name":"CVE-2019-1549","record":{"aliases":["ALPINE-CVE-2019-1549","CLEANSTART-2026-WP77838","DEBIAN-CVE-2019-1549","GHSA-xmjp-8ccm-cf6h","JLSEC-2026-215","UBUNTU-CVE-2019-1549"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenSSL cryptographic library","requires_auth":"none","summary":"OpenSSL's RNG fork protection failed by default, risking shared random states between parent and child processes, potentially compromising cryptographic keys.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openssl","cpe":[{"product":"openssl","vendor":"openssl"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).","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":"Fork Protection","id":"CVE-2019-1549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"openssl:openssl","products":["openssl:openssl"],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":15,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-1550"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-1548"},"products":["OpenSSL"],"published":"2019-09-10","related":[{"cvss_score":10,"headline":"Null dereference in n/a","id":"CVE-2009-3245","kev_date_added":null,"published":"2010-03-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2006-3738","kev_date_added":null,"published":"2006-09-28"},{"cvss_score":9.8,"headline":"Untrusted Sender DN Used as Format String in CMP Response Validation","id":"CVE-2026-63073","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2016-6309","kev_date_added":null,"published":"2016-09-26"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-0799","kev_date_added":null,"published":"2016-03-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-2842","kev_date_added":null,"published":"2016-03-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2003-0545","kev_date_added":null,"published":"2003-10-01"}],"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-09-16","vendors":["OpenSSL"]},"summary":"OpenSSL's RNG fork protection failed by default, risking shared random states between parent and child processes, potentially compromising cryptographic keys.","url":"https://insights.sbomify.com/CVE-2019-1549/"}