{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16241 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16241 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16241 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Nov 2019. 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-2019-16241 and fix it if it is affected.\n\nWhat it is: CVE-2019-16241 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Nov 2019. 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-2019-16241 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-2019-16241/ (Markdown: https://insights.sbomify.com/CVE-2019-16241/index.md)","id":"CVE-2019-16241","markdown":"https://insights.sbomify.com/CVE-2019-16241/index.md","name":"CVE-2019-16241","record":{"aliases":["GHSA-qg5g-43r3-8gpr"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TCL Alcatel Flip 2","requires_auth":"none","summary":"Attackers can bypass PIN authentication on TCL Alcatel Flip 2 devices by creating a specific file in the local temporary directory.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cingular_flip_2_firmware","vendor":"alcatelmobile"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"On TCL Alcatel Cingular Flip 2 B9HUAH1 devices, PIN authentication can be bypassed by creating a special file within the /data/local/tmp/ directory. The System application that implements the lock screen checks for the existence of a specific file and disables PIN authentication if it exists. This file would typically be created via Android Debug Bridge (adb) over USB.","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":"Auth bypass in n/a","id":"CVE-2019-16241","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2019-16242"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-16240"},"products":["n/a"],"published":"2019-11-26","related":[{"cvss_score":6.8,"headline":"Command injection in n/a","id":"CVE-2019-16242","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":6.1,"headline":"Missing authorization in n/a","id":"CVE-2019-16243","kev_date_added":null,"published":"2019-11-26"}],"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 PIN authentication on TCL Alcatel Flip 2 devices by creating a specific file in the local temporary directory.","url":"https://insights.sbomify.com/CVE-2019-16241/"}