# CVE-2013-0490: Privilege escalation in n/a

> Local attackers can exploit an unspecified vulnerability in IBM InfoSphere Guardium S-TAP to gain elevated privileges on DB2 z/OS systems.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f7pq-88x4-j8jf

## What is CVE-2013-0490?

CVE-2013-0490 is a high-severity vulnerability in n/a, published on 27 Feb 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in IBM InfoSphere Guardium S-TAP 8.1 for DB2 on z/OS allows local users to gain privileges via unknown vectors.

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

It affects 1 product.


Products: Ibm Infosphere Guardium.

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

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

## Is CVE-2013-0490 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-3309](https://insights.sbomify.com/CVE-2012-3309/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-3341](https://insights.sbomify.com/CVE-2012-3341/): Cross-site scripting in InfoSphere Guardium (medium 6.4)
- [CVE-2012-3336](https://insights.sbomify.com/CVE-2012-3336/): SQL injection in InfoSphere Guardium (medium 6.3)
- [CVE-2012-2204](https://insights.sbomify.com/CVE-2012-2204/): InfoSphere Guardium aix_ktap module: DoS (medium 5.5)
- [CVE-2012-3337](https://insights.sbomify.com/CVE-2012-3337/): Path traversal in InfoSphere Guardium (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0490 is a high-severity vulnerability in n/a, published on 27 Feb 2013. 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-2013-0490 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-0490/ (Markdown: https://insights.sbomify.com/CVE-2013-0490/index.md)
```

## Sources

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

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