# CVE-2019-14656: Missing authorization in n/a

> Attackers can escalate privileges to admin on Yealink phones by exploiting missing role checks in HTTP POST requests.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-22wm-vgh4-2j44

## What is CVE-2019-14656?

CVE-2019-14656 is a high-severity missing authorization vulnerability in n/a, published on 8 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Yealink phones through 2019-08-04 do not properly check user roles in POST requests. Consequently, the default User account (with a password of user) can make admin requests via HTTP.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2019-14656?

It affects 3 products.


Products: Yeahlink T49g Firmware, Yeahlink T58v Firmware, Yeahlink Vp59 Firmware.

## How do I fix CVE-2019-14656?

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

## Is CVE-2019-14656 being exploited?

There is no known exploitation of CVE-2019-14656 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-14657](https://insights.sbomify.com/CVE-2019-14657/): Path traversal in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14656 and fix it if it is affected.

What it is: CVE-2019-14656 is a high-severity missing authorization vulnerability in n/a, published on 8 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-14656 in the wild and no public exploit code.

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-2019-14656/ (Markdown: https://insights.sbomify.com/CVE-2019-14656/index.md)
```

## Sources

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

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