{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2012-3273 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2012-3273 yet. Limit exposure of the affected software until one is available.","what":"CVE-2012-3273 is a medium-severity vulnerability in n/a, published on 6 Dec 2012. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-3273 and fix it if it is affected.\n\nWhat it is: CVE-2012-3273 is a medium-severity vulnerability in n/a, published on 6 Dec 2012. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2012-3273 in the wild and no public exploit code.\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-2012-3273/ (Markdown: https://insights.sbomify.com/CVE-2012-3273/index.md)","id":"CVE-2012-3273","markdown":"https://insights.sbomify.com/CVE-2012-3273/index.md","name":"CVE-2012-3273","record":{"aliases":["GHSA-h4w2-426f-gchg"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"HP LaserJet printer","requires_auth":"unknown","summary":"Remote attackers can obtain sensitive information from HP LaserJet Pro printers via unspecified vectors, requiring firmware updates.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hp","cpe":[{"product":"laserjet_pro_mfp_m401","vendor":"hp"},{"product":"laserjet_pro_mfp_m425","vendor":"hp"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"Multiple unspecified vulnerabilities on the HP LaserJet Pro 400 MFP M425 with firmware 20120625 and LaserJet 400 M401 with firmware 20120621 allow remote attackers to obtain sensitive information via unknown vectors.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2012-3273","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2012"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2012-3274"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2012-3272"},"products":["n/a"],"published":"2012-12-06","related":[],"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":"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 can obtain sensitive information from HP LaserJet Pro printers via unspecified vectors, requiring firmware updates.","url":"https://insights.sbomify.com/CVE-2012-3273/"}