# CVE-2013-4022: Auth bypass in n/a

> Remote authenticated users can bypass access restrictions in IBM Data Studio and related tools by exploiting insecure cookie storage of authentication information.

- **Severity:** Low 3.5 (`AV:N/AC:M/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:** 25 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gr95-2p5v-jmcg

## What is CVE-2013-4022?

CVE-2013-4022 is a low-severity authentication bypass vulnerability in n/a, published on 25 Sep 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Data Studio Web Console 3.x before 3.2, Optim Performance Manager 5.x before 5.2, InfoSphere Optim Configuration Manager 2.x before 2.2, and DB2 Recovery Expert 2.x store unspecified authentication information in a cookie, which allows remote authenticated users to bypass intended access restrictions via unknown vectors.

Weakness: CWE-255

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

It affects 4 products.


Products: Ibm Data Studio Web Console, Ibm Db2 Recovery Expert, Ibm Infosphere Optim Configuration Manager, Ibm Optim Performance Manager.

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

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

## Is CVE-2013-4022 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4024](https://insights.sbomify.com/CVE-2013-4024/): Information disclosure in n/a (medium 4.3)
- [CVE-2013-4025](https://insights.sbomify.com/CVE-2013-4025/): Security feature bypass in n/a (low 1.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4022 is a low-severity authentication bypass vulnerability in n/a, published on 25 Sep 2013. 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-4022 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-4022/ (Markdown: https://insights.sbomify.com/CVE-2013-4022/index.md)
```

## Sources

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

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