{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-33374 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-33374 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-33374 is a critical authentication bypass vulnerability in n/a, published on 14 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-33374 and fix it if it is affected.\n\nWhat it is: CVE-2024-33374 is a critical authentication bypass vulnerability in n/a, published on 14 Jun 2024. 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-2024-33374 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-2024-33374/ (Markdown: https://insights.sbomify.com/CVE-2024-33374/index.md)","id":"CVE-2024-33374","markdown":"https://insights.sbomify.com/CVE-2024-33374/index.md","name":"CVE-2024-33374","record":{"aliases":["GHSA-xjjc-xf36-3jp9"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LB-LINK router","requires_auth":"none","summary":"Attackers can access the root terminal without authentication via the UART interface on LB-LINK BL-W1210M v2.0 routers.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Incorrect access control in the UART/Serial interface on the LB-LINK BL-W1210M v2.0 router allows attackers to access the root terminal without authentication.","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-2024-33374","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2024-33375"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2024-33373"},"products":["n/a"],"published":"2024-06-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can access the root terminal without authentication via the UART interface on LB-LINK BL-W1210M v2.0 routers.","url":"https://insights.sbomify.com/CVE-2024-33374/"}