# CVE-2013-5433: Hardcoded credentials in n/a

> Hardcoded database credentials in IBM InfoSphere Optim allow authenticated users to access sensitive information via XML fields.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **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:** 12 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-74gp-p893-qhq9

## What is CVE-2013-5433?

CVE-2013-5433 is a medium-severity vulnerability in n/a, published on 12 Aug 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Data Growth Solution for JD Edwards EnterpriseOne in IBM InfoSphere Optim 3.0 through 9.1 has hardcoded database credentials, which allows remote authenticated users to obtain sensitive information by reading an unspecified field in an XML document.

Weakness: CWE-255

## Which versions are affected by CVE-2013-5433?

It affects 1 product.


Products: Ibm Infosphere Optim Data Growth Solution for Siebel Crm.

## How do I fix CVE-2013-5433?

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

## Is CVE-2013-5433 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5433 and fix it if it is affected.

What it is: CVE-2013-5433 is a medium-severity vulnerability in n/a, published on 12 Aug 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-5433 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-2013-5433/ (Markdown: https://insights.sbomify.com/CVE-2013-5433/index.md)
```

## Sources

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

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