{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-43523 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2021-43523 is a critical cross-site scripting vulnerability in n/a, published on 10 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-43523 and fix it if it is affected.\n\nWhat it is: CVE-2021-43523 is a critical cross-site scripting vulnerability in n/a, published on 10 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-43523 exists.\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-2021-43523/ (Markdown: https://insights.sbomify.com/CVE-2021-43523/index.md)","id":"CVE-2021-43523","markdown":"https://insights.sbomify.com/CVE-2021-43523/index.md","name":"CVE-2021-43523","record":{"aliases":["AZL-6928","DEBIAN-CVE-2021-43523","GHSA-65xv-vmv6-8r3f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"uClibc C library","requires_auth":"none","summary":"Attackers can inject malicious content via DNS responses in uClibc, leading to remote code execution or XSS in applications using affected functions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"uclibc-ng","vendor":"uclibc-ng_project"},{"product":"uclibc","vendor":"uclibc"}],"cvss":{"score":9.6,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In uClibc and uClibc-ng before 1.0.39, incorrect handling of special characters in domain names returned by DNS servers via gethostbyname, getaddrinfo, gethostbyaddr, and getnameinfo can lead to output of wrong hostnames (leading to domain hijacking) or injection into applications (leading to remote code execution, XSS, applications crashes, etc.). In other words, a validation step, which is expected in any stub resolver, does not occur.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Cross-site scripting in n/a","id":"CVE-2021-43523","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in NSS","id":"CVE-2021-43527"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-43522"},"products":["n/a"],"published":"2021-11-10","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2016-2224","kev_date_added":null,"published":"2017-03-24"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2016-2225","kev_date_added":null,"published":"2017-03-24"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2016-6264","kev_date_added":null,"published":"2017-01-27"},{"cvss_score":7.3,"headline":"uClibc-ng Integer Overflow or Wraparound","id":"CVE-2021-27419","kev_date_added":null,"published":"2022-05-03"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2022-30295","kev_date_added":null,"published":"2022-05-06"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-05","vendors":["n/a"]},"summary":"Attackers can inject malicious content via DNS responses in uClibc, leading to remote code execution or XSS in applications using affected functions.","url":"https://insights.sbomify.com/CVE-2021-43523/"}