# CVE-2014-1219: Auth bypass in n/a

> Remote attackers can hijack user sessions by exploiting predictable session token substrings in CA 2E Web Option.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **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:** 13 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vfgg-62x5-92v2

## What is CVE-2014-1219?

CVE-2014-1219 is a medium-severity authentication bypass vulnerability in n/a, published on 13 Feb 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CA 2E Web Option r8.1.2 accepts a predictable substring of a W2E_SSNID session token in place of the entire token, which allows remote attackers to hijack sessions by changing characters at the end of this substring, as demonstrated by terminating a session via a modified SSNID parameter to web2edoc/close.htm.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Broadcom 2e Web Option.

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

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

## Is CVE-2014-1219 being exploited?

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

Public exploit code:

- CA 2E Web Option 8.1.2 - Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-1219 is a medium-severity authentication bypass vulnerability in n/a, published on 13 Feb 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-1219 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-1219/ (Markdown: https://insights.sbomify.com/CVE-2014-1219/index.md)
```

## Sources

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

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