# CVE-2024-31747: Security feature bypass in n/a

> A physically proximate attacker can bypass the phone lock screen via the Walkie Talkie menu, compromising device security.

- **Severity:** Low 2.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Apr 2024
- **Updated:** 4 Nov 2024
- **Also known as:** GHSA-23rc-q984-j9jx

## What is CVE-2024-31747?

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.

### Official 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.

## Which versions are affected by CVE-2024-31747?

It affects 1 product.


Products: Yealink Vp59 Firmware.

## How do I fix CVE-2024-31747?

No fix has been published for CVE-2024-31747 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-31747 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31747 exists.

## Other vulnerabilities in n/a

- [CVE-2024-28442](https://insights.sbomify.com/CVE-2024-28442/): Path traversal in n/a (high 7.5)
- [CVE-2024-30939](https://insights.sbomify.com/CVE-2024-30939/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31747 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31747 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-31747/ (Markdown: https://insights.sbomify.com/CVE-2024-31747/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-31747
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-31747
- OSV: https://osv.dev/vulnerability/CVE-2024-31747

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-31747/
Summaries are generated and may contain mistakes; the official description above is the record.