{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-3142 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2015-3142 is a medium-severity vulnerability in n/a, published on 26 Jun 2017. 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-2015-3142 and fix it if it is affected.\n\nWhat it is: CVE-2015-3142 is a medium-severity vulnerability in n/a, published on 26 Jun 2017. 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-2015-3142 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-2015-3142/ (Markdown: https://insights.sbomify.com/CVE-2015-3142/index.md)","id":"CVE-2015-3142","markdown":"https://insights.sbomify.com/CVE-2015-3142/index.md","name":"CVE-2015-3142","record":{"aliases":["GHSA-fpvf-mw5r-q2rm"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ABRT coredump processor","requires_auth":"low_privilege","summary":"Local attackers can read sensitive core dump files by exploiting improper ownership checks in the ABRT coredump processor.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"automatic_bug_reporting_tool","vendor":"redhat"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The kernel-invoked coredump processor in Automatic Bug Reporting Tool (ABRT) does not properly check the ownership of files before writing core dumps to them, which allows local users to obtain sensitive information by leveraging write permissions to the working directory of a crashed application.","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-2015-3142","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":5,"next":{"headline":"Auth bypass in n/a","id":"CVE-2015-3143"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2015-3141"},"products":["n/a"],"published":"2017-06-26","related":[{"cvss_score":7.8,"headline":"Path traversal in ABRT","id":"CVE-2015-1869","kev_date_added":null,"published":"2020-01-14"},{"cvss_score":7.8,"headline":"Path traversal in ABRT","id":"CVE-2015-3151","kev_date_added":null,"published":"2020-01-14"},{"cvss_score":7.8,"headline":"Privilege escalation in ABRT","id":"CVE-2015-3159","kev_date_added":null,"published":"2020-01-14"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2015-3315","kev_date_added":null,"published":"2017-06-26"},{"cvss_score":7.1,"headline":"Path traversal in ABRT","id":"CVE-2015-3150","kev_date_added":null,"published":"2020-01-14"},{"cvss_score":7,"headline":"Race condition in n/a","id":"CVE-2015-1862","kev_date_added":null,"published":"2018-02-09"},{"cvss_score":6.9,"headline":"Race condition in n/a","id":"CVE-2012-5660","kev_date_added":null,"published":"2013-03-12"}],"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-06","vendors":["n/a"]},"summary":"Local attackers can read sensitive core dump files by exploiting improper ownership checks in the ABRT coredump processor.","url":"https://insights.sbomify.com/CVE-2015-3142/"}