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

> Attackers on the local network can access internal interfaces using a hardcoded default password to execute unauthorized actions on AudioCodes Mediant devices.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2h52-m7f3-9vxw

## What is CVE-2019-9229?

CVE-2019-9229 is a high-severity vulnerability in n/a, published on 19 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on AudioCodes Mediant 500L-MSBR, 500-MBSR, M800B-MSBR and 800C-MSBR devices with firmware versions F7.20A to F7.20A.251. An internal interface exposed to the link-local address 169.254.254.253 allows attackers in the local network to access multiple quagga VTYs. Attackers can authenticate with the default 1234 password that cannot be changed, and can execute malicious and unauthorized actions.

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

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

It affects 4 products.


Products: Audiocodes Median 500-Msbr Firmware, Audiocodes Median 500l-Msbr Firmware, Audiocodes Median 800c-Msbr Firmware, Audiocodes Median M800b-Msbr Firmware.

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

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

## Is CVE-2019-9229 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9228](https://insights.sbomify.com/CVE-2019-9228/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9229 is a high-severity vulnerability in n/a, published on 19 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9229 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-9229/ (Markdown: https://insights.sbomify.com/CVE-2019-9229/index.md)
```

## Sources

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

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