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

> Hardcoded database credentials in Teradata Viewpoint allow attackers to compromise the system and access sensitive data.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jpm6-hpj8-49xp

## What is CVE-2019-6499?

CVE-2019-6499 is a high-severity vulnerability in n/a, published on 21 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Teradata Viewpoint before 14.0 and 16.20.00.02-b80 contains a hardcoded password of TDv1i2e3w4 for the viewpoint database account (in viewpoint-portal\conf\server.xml) that could potentially be exploited by malicious users to compromise the affected system.

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

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

It affects 1 product.


Products: Teradata Viewpoint.

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

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

## Is CVE-2019-6499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6499 is a high-severity vulnerability in n/a, published on 21 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6499 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-6499/ (Markdown: https://insights.sbomify.com/CVE-2019-6499/index.md)
```

## Sources

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

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