{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-2599 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-2599 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-2599 is a medium-severity vulnerability in n/a, published on 31 Aug 2014. 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-2013-2599 and fix it if it is affected.\n\nWhat it is: CVE-2013-2599 is a medium-severity vulnerability in n/a, published on 31 Aug 2014. 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-2013-2599 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-2013-2599/ (Markdown: https://insights.sbomify.com/CVE-2013-2599/index.md)","id":"CVE-2013-2599","markdown":"https://insights.sbomify.com/CVE-2013-2599/index.md","name":"CVE-2013-2599","record":{"aliases":["GHSA-7h3j-c79g-3vfx"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Android OS","requires_auth":"low_privilege","summary":"Attackers with local access can retrieve sensitive disk-encryption passwords from debug logs in specific Android builds.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"android-msm","vendor":"codeaurora"}],"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":"A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption passwords via a logcat call.","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-2013-2599","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2013"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2013-2600"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2013-2598"},"products":["n/a"],"published":"2014-08-31","related":[{"cvss_score":8.4,"headline":"Code Aurora ACDB Audio Driver Stack-based Buffer Overflow","id":"CVE-2013-2597","kev_date_added":"2022-09-15","published":"2014-08-31"},{"cvss_score":7.8,"headline":"Integer overflow in n/a","id":"CVE-2013-4736","kev_date_added":null,"published":"2014-02-10"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2013-2595","kev_date_added":null,"published":"2014-08-31"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2014-0972","kev_date_added":null,"published":"2014-08-01"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-2013-4738","kev_date_added":null,"published":"2014-02-03"},{"cvss_score":6.9,"headline":"Privilege escalation in n/a","id":"CVE-2013-6123","kev_date_added":null,"published":"2014-01-14"},{"cvss_score":6.6,"headline":"Security feature bypass in n/a","id":"CVE-2013-2598","kev_date_added":null,"published":"2014-08-31"}],"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":"Attackers with local access can retrieve sensitive disk-encryption passwords from debug logs in specific Android builds.","url":"https://insights.sbomify.com/CVE-2013-2599/"}