# CVE-2019-12327: Hardcoded credentials in n/a

> Hardcoded credentials in the Akuvox R50P VoIP phone allow attackers to gain unauthorized access via telnet, leading to device takeover.

- **Severity:** High 7.2 (`CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:H/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9f6m-vqgf-833g

## What is CVE-2019-12327?

CVE-2019-12327 is a high-severity vulnerability in n/a, published on 22 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Hardcoded credentials in the Akuvox R50P VoIP phone 50.0.6.156 allow an attacker to get access to the device via telnet. The telnet service is running on port 2323; it cannot be turned off and the credentials cannot be changed.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Akuvox Sp-R50p Firmware.

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

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

## Is CVE-2019-12327 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12324](https://insights.sbomify.com/CVE-2019-12324/): Command injection in n/a (high 7.2)
- [CVE-2019-12326](https://insights.sbomify.com/CVE-2019-12326/): File upload in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12327 is a high-severity vulnerability in n/a, published on 22 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12327 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-12327/ (Markdown: https://insights.sbomify.com/CVE-2019-12327/index.md)
```

## Sources

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

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