# CVE-2013-5444: Information disclosure in n/a

> Remote attackers can read encrypted credentials from IBM Cognos Express servers, exposing sensitive authentication data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j648-m8g6-h7mq

## What is CVE-2013-5444?

CVE-2013-5444 is a medium-severity vulnerability in n/a, published on 25 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The server in IBM Cognos Express 9.0 before IFIX 2, 9.5 before IFIX 2, 10.1 before IFIX 2, and 10.2.1 before FP1 allows remote attackers to read encrypted credentials via unspecified vectors.

Weakness: CWE-310

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

It affects 1 product.


Products: Ibm Cognos Express.

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

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

## Is CVE-2013-5444 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0557](https://insights.sbomify.com/CVE-2010-0557/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2013-5443](https://insights.sbomify.com/CVE-2013-5443/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-5445](https://insights.sbomify.com/CVE-2013-5445/): Weak cryptography in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5444 is a medium-severity vulnerability in n/a, published on 25 Mar 2014. 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-2013-5444 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-5444/ (Markdown: https://insights.sbomify.com/CVE-2013-5444/index.md)
```

## Sources

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

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