{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-3831 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-3831 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-3831 is a high-severity denial of service vulnerability in Google Android, published on 5 Aug 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-3831 and fix it if it is affected.\n\nWhat it is: CVE-2016-3831 is a high-severity denial of service vulnerability in Google Android, published on 5 Aug 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-3831 in the wild and no public exploit code.\n\nAffected product: Google Android. 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-2016-3831/ (Markdown: https://insights.sbomify.com/CVE-2016-3831/index.md)","id":"CVE-2016-3831","markdown":"https://insights.sbomify.com/CVE-2016-3831/index.md","name":"CVE-2016-3831","record":{"aliases":["GHSA-74hv-prrr-hxjg","UBUNTU-CVE-2016-3831"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Android telephony","requires_auth":"none","summary":"Remote attackers can crash Android devices by sending a specific NITZ time value, causing a denial of service due to mishandled system clock logic.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"google_android","cpe":[{"product":"android","vendor":"google"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The telephony component in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-08-01 allows remote attackers to cause a denial of service (device crash) via a NITZ time value of 2038-01-19 or later that is mishandled by the system clock, aka internal bug 29083635, related to a \"Year 2038 problem.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2016-3831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"denial_of_service","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2016-3832"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2016-3830"},"products":["n/a"],"published":"2016-08-05","related":[{"cvss_score":8.8,"headline":"Google Pixel Improper Authorization","id":"CVE-2026-58704","kev_date_added":"2026-09-16","published":"2026-09-15"},{"cvss_score":8.8,"headline":"Android Runtime Use-After-Free","id":"CVE-2025-48543","kev_date_added":"2025-09-04","published":"2025-09-04"},{"cvss_score":8.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2023-35674","kev_date_added":"2023-09-13","published":"2023-09-11"},{"cvss_score":8.4,"headline":"Android Framework Integer Overflow","id":"CVE-2025-48595","kev_date_added":"2026-06-02","published":"2026-06-01"},{"cvss_score":8.1,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-32896","kev_date_added":"2024-06-13","published":"2024-06-13"},{"cvss_score":7.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2025-48572","kev_date_added":"2025-12-02","published":"2025-12-08"},{"cvss_score":7.8,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-29748","kev_date_added":"2024-04-04","published":"2024-04-05"}],"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":"Remote attackers can crash Android devices by sending a specific NITZ time value, causing a denial of service due to mishandled system clock logic.","url":"https://insights.sbomify.com/CVE-2016-3831/"}