{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-31147 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-31147 is a medium-severity vulnerability in Fedoraproject Fedora, published on 25 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-31147 and fix it if it is affected.\n\nWhat it is: CVE-2023-31147 is a medium-severity vulnerability in Fedoraproject Fedora, published on 25 May 2023. 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-2023-31147 in the wild and no public exploit code.\n\nAffected product: Fedoraproject Fedora. 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-2023-31147/ (Markdown: https://insights.sbomify.com/CVE-2023-31147/index.md)","id":"CVE-2023-31147","markdown":"https://insights.sbomify.com/CVE-2023-31147/index.md","name":"CVE-2023-31147","record":{"aliases":["AZL-26869","AZL-26870","AZL-26871","AZL-26874","AZL-26875","AZL-26876","AZL-34776","AZL-43702","DEBIAN-CVE-2023-31147","ECHO-ff3d-b3d4-b3c9","GHSA-8r8p-23f3-64c2","OESA-2023-1339","OESA-2023-1340"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"c-ares DNS resolver","requires_auth":"none","summary":"Attackers can predict DNS query IDs due to weak randomness, enabling cache poisoning or spoofing attacks against applications using c-ares.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"c-ares","vendor":"c-ares_project"},{"product":"fedora","vendor":"fedoraproject"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"c-ares is an asynchronous resolver library. When /dev/urandom or RtlGenRandom() are unavailable, c-ares uses rand() to generate random numbers used for DNS query ids. This is not a CSPRNG, and it is also not seeded by srand() so will generate predictable output. Input from the random number generator is fed into a non-compilant RC4 implementation and may not be as strong as the original RC4 implementation. No attempt is made to look for modern OS-provided CSPRNGs like arc4random() that is widely available. This issue has been fixed in version 1.19.1.","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":"Insufficient randomness in generation of DNS query IDs in c-ares","id":"CVE-2023-31147","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fedoraproject:fedora","products":["fedoraproject:fedora"],"type":"weak_cryptography","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Improper Input Validation in Web Interface","id":"CVE-2023-31148"},"packages":[],"prev":{"headline":"Vyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignment","id":"CVE-2023-31146"},"products":["c-ares"],"published":"2023-05-25","related":[{"cvss_score":8.6,"headline":"Memory corruption in c-ares","id":"CVE-2022-4904","kev_date_added":null,"published":"2023-03-06"},{"cvss_score":7.5,"headline":"0-byte UDP payload DoS in c-ares","id":"CVE-2023-32067","kev_date_added":null,"published":"2023-05-25"},{"cvss_score":7.5,"headline":"Uncontrolled Resource Consumption in node","id":"CVE-2020-8277","kev_date_added":null,"published":"2020-11-19"},{"cvss_score":5.6,"headline":"Other in c-ares","id":"CVE-2021-3672","kev_date_added":null,"published":"2021-11-23"},{"cvss_score":4.1,"headline":"Buffer Underwrite in ares_inet_net_pton()","id":"CVE-2023-31130","kev_date_added":null,"published":"2023-05-25"},{"cvss_score":3.7,"headline":"AutoTools does not set CARES_RANDOM_FILE during cross compilation","id":"CVE-2023-31124","kev_date_added":null,"published":"2023-05-25"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["c-ares"]},"summary":"Attackers can predict DNS query IDs due to weak randomness, enabling cache poisoning or spoofing attacks against applications using c-ares.","url":"https://insights.sbomify.com/CVE-2023-31147/"}