{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-2567 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-2567 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-2567 is a low-severity vulnerability in n/a, published on 13 Apr 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-2016-2567 and fix it if it is affected.\n\nWhat it is: CVE-2016-2567 is a low-severity vulnerability in n/a, published on 13 Apr 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-2016-2567 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-2016-2567/ (Markdown: https://insights.sbomify.com/CVE-2016-2567/index.md)","id":"CVE-2016-2567","markdown":"https://insights.sbomify.com/CVE-2016-2567/index.md","name":"CVE-2016-2567","record":{"aliases":["GHSA-mgxj-2m8w-mj9x"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Android kernel","requires_auth":"low_privilege","summary":"Attackers can bypass URL filtering in Samsung Android kernels by inserting exceptional URLs in query strings, allowing access to blocked sites.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"galaxy_note_3_firmware","vendor":"samsung"},{"product":"galaxy_s6_firmware","vendor":"samsung"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"secfilter in the Samsung kernel for Android on SM-N9005 build N9005XXUGBOB6 (Note 3) and SM-G920F build G920FXXU2COH2 (Galaxy S6) devices allows attackers to bypass URL filtering by inserting an \"exceptional URL\" in the query string, as demonstrated by the http://should-have-been-filtered.example.com/?http://google.com URL.","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":"Security feature bypass in n/a","id":"CVE-2016-2567","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2016-2568"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2016-2566"},"products":["n/a"],"published":"2017-04-13","related":[{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2016-4030","kev_date_added":null,"published":"2017-04-13"},{"cvss_score":6.8,"headline":"Missing authorization in n/a","id":"CVE-2016-4031","kev_date_added":null,"published":"2017-04-13"},{"cvss_score":5.5,"headline":"Null dereference in n/a","id":"CVE-2016-2036","kev_date_added":null,"published":"2017-04-13"},{"cvss_score":4.6,"headline":"Security feature bypass in n/a","id":"CVE-2016-4032","kev_date_added":null,"published":"2017-04-13"}],"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-05","vendors":["n/a"]},"summary":"Attackers can bypass URL filtering in Samsung Android kernels by inserting exceptional URLs in query strings, allowing access to blocked sites.","url":"https://insights.sbomify.com/CVE-2016-2567/"}