{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-3192 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2010-3192 is a medium-severity vulnerability in Gnu Glibc, published on 12 Oct 2010. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-3192 and fix it if it is affected.\n\nWhat it is: CVE-2010-3192 is a medium-severity vulnerability in Gnu Glibc, published on 12 Oct 2010. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2010-3192 in the wild and no public exploit code.\n\nAffected product: Gnu Glibc. 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-2010-3192/ (Markdown: https://insights.sbomify.com/CVE-2010-3192/index.md)","id":"CVE-2010-3192","markdown":"https://insights.sbomify.com/CVE-2010-3192/index.md","name":"CVE-2010-3192","record":{"aliases":["GHSA-388x-h72v-g58j","UBUNTU-CVE-2010-3192"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GNU C Library","requires_auth":"none","summary":"Attackers can obtain sensitive process memory information via stack protection mechanisms when executing incorrect programs, potentially exposing argv[0] and backtraces.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"glibc","vendor":"gnu"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Certain run-time memory protection mechanisms in the GNU C Library (aka glibc or libc6) print argv[0] and backtrace information, which might allow context-dependent attackers to obtain sensitive information from process memory by executing an incorrect program, as demonstrated by a setuid program that contains a stack-based buffer overflow error, related to the __fortify_fail function in debug/fortify_fail.c, and the __stack_chk_fail (aka stack protection) and __chk_fail (aka FORTIFY_SOURCE) implementations.","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":"Information disclosure in n/a","id":"CVE-2010-3192","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"gnu:glibc","products":["gnu:glibc"],"type":"information_disclosure","year":"2010"},"n_packages":0,"n_references":8,"next":{"headline":"Other in n/a","id":"CVE-2010-3193"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2010-3191"},"products":["n/a"],"published":"2010-10-12","related":[{"cvss_score":9.8,"headline":"scanf %mc off-by-one heap buffer overflow","id":"CVE-2026-5450","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-25139","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-1999-0199","kev_date_added":null,"published":"2020-10-06"},{"cvss_score":9.8,"headline":"Security feature bypass in glibc","id":"CVE-2019-1010022","kev_date_added":null,"published":"2019-07-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2005-3590","kev_date_added":null,"published":"2019-04-10"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-18269","kev_date_added":null,"published":"2018-05-18"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2018-11236","kev_date_added":null,"published":"2018-05-18"}],"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":["n/a"]},"summary":"Attackers can obtain sensitive process memory information via stack protection mechanisms when executing incorrect programs, potentially exposing argv[0] and backtraces.","url":"https://insights.sbomify.com/CVE-2010-3192/"}