# CVE-2012-0264: Other in n/a

> Remote attackers can exploit improper session cookie management in op5 Monitor to achieve unspecified impacts.

- **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:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 31 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-99gw-rhm2-2xpx

## What is CVE-2012-0264?

CVE-2012-0264 is a critical vulnerability in n/a, published on 31 Dec 2013. It can be exploited over the network.

### Official description

op5 Monitor and op5 Appliance before 5.5.0 do not properly manage session cookies, which allows remote attackers to have an unspecified impact via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2012-0264?

It affects 1 product.


Products: Op5 Monitor.

## How do I fix CVE-2012-0264?

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

## Is CVE-2012-0264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0261](https://insights.sbomify.com/CVE-2012-0261/): Command injection in n/a (critical 10.0)
- [CVE-2012-0262](https://insights.sbomify.com/CVE-2012-0262/): Command injection in n/a (critical 10.0)
- [CVE-2021-40272](https://insights.sbomify.com/CVE-2021-40272/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2013-6141](https://insights.sbomify.com/CVE-2013-6141/): Missing authorization in n/a (medium 5.0)
- [CVE-2014-4907](https://insights.sbomify.com/CVE-2014-4907/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0264 and fix it if it is affected.

What it is: CVE-2012-0264 is a critical vulnerability in n/a, published on 31 Dec 2013. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2012-0264 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-2012-0264/ (Markdown: https://insights.sbomify.com/CVE-2012-0264/index.md)
```

## Sources

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

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