# CVE-2006-6836: Other in n/a

> Unspecified vulnerabilities in IBM OS/400 ASN.1 parsing allow attackers to potentially compromise the system via unknown vectors.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 1 Jan 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m2ww-g2pp-wv55

## What is CVE-2006-6836?

CVE-2006-6836 is a critical vulnerability in n/a, published on 1 Jan 2007. 

### Official description

Multiple unspecified vulnerabilities in osp-cert in IBM OS/400 V5R3M0 have unspecified impact and attack vectors, related to ASN.1 parsing.

## Which versions are affected by CVE-2006-6836?

It affects 1 product.


Products: Ibm Os 400.

## How do I fix CVE-2006-6836?

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

## Is CVE-2006-6836 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3537](https://insights.sbomify.com/CVE-2007-3537/): Information disclosure in n/a (high 7.8)
- [CVE-2007-0442](https://insights.sbomify.com/CVE-2007-0442/): Other in n/a (medium 5.0)
- [CVE-2005-1182](https://insights.sbomify.com/CVE-2005-1182/): Denial of service in n/a (medium 5.0)
- [CVE-2008-2709](https://insights.sbomify.com/CVE-2008-2709/): Memory corruption in n/a (medium 4.7)
- [CVE-2008-0694](https://insights.sbomify.com/CVE-2008-0694/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6836 and fix it if it is affected.

What it is: CVE-2006-6836 is a critical vulnerability in n/a, published on 1 Jan 2007. 
Exploitation: There is no known exploitation of CVE-2006-6836 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-2006-6836/ (Markdown: https://insights.sbomify.com/CVE-2006-6836/index.md)
```

## Sources

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

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