{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2007-6249 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2007-6249 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-6249 is a low-severity vulnerability in n/a, published on 15 Dec 2007. 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-2007-6249 and fix it if it is affected.\n\nWhat it is: CVE-2007-6249 is a low-severity vulnerability in n/a, published on 15 Dec 2007. 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-2007-6249 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-2007-6249/ (Markdown: https://insights.sbomify.com/CVE-2007-6249/index.md)","id":"CVE-2007-6249","markdown":"https://insights.sbomify.com/CVE-2007-6249/index.md","name":"CVE-2007-6249","record":{"aliases":["GHSA-vfqg-qqv4-ghx2"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Gentoo Linux package manager","requires_auth":"low_privilege","summary":"Local users can read sensitive information from Portage merge files due to weak permissions caused by umask reliance.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"portage","vendor":"gentoo"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"etc-update in Portage before 2.1.3.11 on Gentoo Linux relies on the umask to set permissions for the merge file, often resulting in permissions weaker than those of the original files, which might allow local users to obtain sensitive information by reading the merge file.","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-2007-6249","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2007"},"n_packages":0,"n_references":8,"next":{"headline":"Memory corruption in n/a","id":"CVE-2007-6250"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2007-6247"},"products":["n/a"],"published":"2007-12-15","related":[{"cvss_score":9.8,"headline":"Gentoo Portage missing PGP validation of executed code","id":"CVE-2016-20021","kev_date_added":null,"published":"2024-01-12"},{"cvss_score":9.3,"headline":"Gentoo Portage does not verify X.509 certificates from SSL servers","id":"CVE-2013-2100","kev_date_added":null,"published":"2014-09-29"},{"cvss_score":7.1,"headline":"Privilege escalation in n/a","id":"CVE-2004-2778","kev_date_added":null,"published":"2017-06-27"},{"cvss_score":6.9,"headline":"Path traversal in n/a","id":"CVE-2008-4394","kev_date_added":null,"published":"2008-10-10"},{"cvss_score":5.5,"headline":"Race condition in n/a","id":"CVE-2019-20384","kev_date_added":null,"published":"2020-01-20"}],"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-08-07","vendors":["n/a"]},"summary":"Local users can read sensitive information from Portage merge files due to weak permissions caused by umask reliance.","url":"https://insights.sbomify.com/CVE-2007-6249/"}