{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31747 exists.","fix":"No fix has been published for CVE-2024-31747 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-31747 is a low-severity vulnerability in n/a, published on 29 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-31747 and fix it if it is affected.\n\nWhat it is: CVE-2024-31747 is a low-severity vulnerability in n/a, published on 29 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31747 exists.\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-31747/ (Markdown: https://insights.sbomify.com/CVE-2024-31747/index.md)","id":"CVE-2024-31747","markdown":"https://insights.sbomify.com/CVE-2024-31747/index.md","name":"CVE-2024-31747","record":{"aliases":["GHSA-23rc-q984-j9jx"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yealink Teams Phone","requires_auth":"none","summary":"A physically proximate attacker can bypass the phone lock screen via the Walkie Talkie menu, compromising device security.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vp59_firmware","vendor":"yealink"}],"cvss":{"score":2.1,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[],"description":"An issue in Yealink VP59 Microsoft Teams Phone firmware 91.15.0.118 (fixed in 122.15.0.142) allows a physically proximate attacker to disable the phone lock via the Walkie Talkie menu option.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2024-31747","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2024-31750"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2024-31744"},"products":["n/a"],"published":"2024-04-29","related":[{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2024-28442","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2024-30939","kev_date_added":null,"published":"2024-04-25"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-04","vendors":["n/a"]},"summary":"A physically proximate attacker can bypass the phone lock screen via the Walkie Talkie menu, compromising device security.","url":"https://insights.sbomify.com/CVE-2024-31747/"}