{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.hadoop:hadoop-client. It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-3376 in the wild and no public exploit code.","fix":"Upgrade org.apache.hadoop:hadoop-client to 2.0.1-alpha or later.","what":"CVE-2012-3376 is a high-severity missing authorization vulnerability in n/a, published on 12 Jul 2012. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-3376 and fix it if it is affected.\n\nWhat it is: CVE-2012-3376 is a high-severity missing authorization vulnerability in n/a, published on 12 Jul 2012. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2012-3376 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.hadoop:hadoop-client (Maven): affected from 2.0.0-alpha; fixed in 2.0.1-alpha\n- org.apache.hadoop:hadoop-client (Maven): affected from 2.0.0-alpha; fixed in 2.0.1-alpha\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-2012-3376/ (Markdown: https://insights.sbomify.com/CVE-2012-3376/index.md)","id":"CVE-2012-3376","markdown":"https://insights.sbomify.com/CVE-2012-3376/index.md","name":"CVE-2012-3376","record":{"aliases":["GHSA-qmh2-h7r6-gm6q"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Hadoop DataNode","requires_auth":"low_privilege","summary":"Remote attackers with valid Kerberos tickets can bypass block access controls to read or modify arbitrary Hadoop data blocks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"hadoop","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"DataNodes in Apache Hadoop 2.0.0 alpha does not check the BlockTokens of clients when Kerberos is enabled and the DataNode has checked out the same BlockPool twice from a NodeName, which might allow remote clients to read arbitrary blocks, write to blocks to which they only have read access, and have other unspecified impacts.","ecosystems":["Maven"],"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":"Client BlockTokens not checked in Apache Hadoop","id":"CVE-2012-3376","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2012"},"n_packages":2,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2012-3377"},"packages":[{"ecosystem":"Maven","fixed":["2.0.1-alpha"],"introduced":["2.0.0-alpha"],"last_affected":[],"package":"org.apache.hadoop:hadoop-client","purl":null,"source":"GHSA-qmh2-h7r6-gm6q"},{"ecosystem":"Maven","fixed":["2.0.1-alpha"],"introduced":["2.0.0-alpha"],"last_affected":[],"package":"org.apache.hadoop:hadoop-client","purl":"pkg:maven/org.apache.hadoop/hadoop-client","source":"GHSA-qmh2-h7r6-gm6q"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2012-3375"},"products":["n/a"],"published":"2012-07-12","related":[{"cvss_score":9.8,"headline":"Command injection in org.apache.hadoop.fs.FileUtil.unTarUsingTar","id":"CVE-2022-25168","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":9.8,"headline":"Heap buffer overflow in libhdfs native library","id":"CVE-2021-37404","kev_date_added":null,"published":"2022-06-13"},{"cvss_score":9.8,"headline":"Arbitrary file write in FileUtil#unpackEntries on Windows","id":"CVE-2022-26612","kev_date_added":null,"published":"2022-04-07"},{"cvss_score":9.8,"headline":"Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT","id":"CVE-2019-17195","kev_date_added":null,"published":"2019-10-15"},{"cvss_score":9.8,"headline":"Exposure of Sensitive Information in Hadoop","id":"CVE-2017-15718","kev_date_added":null,"published":"2018-01-24"},{"cvss_score":9.8,"headline":"Use of a Broken or Risky Cryptographic Algorithm in Apache Hadoop","id":"CVE-2012-4449","kev_date_added":null,"published":"2017-10-30"},{"cvss_score":9.8,"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Apache Hadoop","id":"CVE-2016-3086","kev_date_added":null,"published":"2017-09-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-06","vendors":["n/a"]},"summary":"Remote attackers with valid Kerberos tickets can bypass block access controls to read or modify arbitrary Hadoop data blocks.","url":"https://insights.sbomify.com/CVE-2012-3376/"}