# CVE-2014-0609: Other in n/a

> Unspecified vulnerability in Novell Open Enterprise Server for Linux with unknown impact and attack 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:** 17 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-88pf-qwh4-43fc

## What is CVE-2014-0609?

CVE-2014-0609 is a critical vulnerability in n/a, published on 17 Aug 2014. 

### Official description

Unspecified vulnerability in Novell Open Enterprise Server (OES) 11 SP1 before Scheduled Maintenance Update 9415 and 11 SP2 before Scheduled Maintenance Update 9413 for Linux has unknown impact and attack vectors.

## Which versions are affected by CVE-2014-0609?

It affects 1 product.


Products: Novell Open Enterprise Server.

## How do I fix CVE-2014-0609?

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

## Is CVE-2014-0609 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0598](https://insights.sbomify.com/CVE-2014-0598/): Path traversal in n/a (critical 10.0)
- [CVE-2017-5182](https://insights.sbomify.com/CVE-2017-5182/): Path traversal in Open Enterprise Server (high 7.5)
- [CVE-2011-4194](https://insights.sbomify.com/CVE-2011-4194/): Memory corruption in n/a (high 7.5)
- [CVE-2005-3655](https://insights.sbomify.com/CVE-2005-3655/): Memory corruption in n/a (high 7.5)
- [CVE-2014-0599](https://insights.sbomify.com/CVE-2014-0599/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0609 and fix it if it is affected.

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

## Sources

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

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