# CVE-2017-12965: Auth bypass in n/a

> Remote attackers can hijack web sessions in Apache2Triad by manipulating the PHPSESSID parameter, leading to account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jprx-chhf-5262

## What is CVE-2017-12965?

CVE-2017-12965 is a critical authentication bypass vulnerability in n/a, published on 23 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Session fixation vulnerability in Apache2Triad 1.5.4 allows remote attackers to hijack web sessions via the PHPSESSID parameter.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2017-12965?

It affects 1 product.


Products: Apache2triad Apache2triad.

## How do I fix CVE-2017-12965?

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

## Is CVE-2017-12965 being exploited?

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

Public exploit code:

- Apache2Triad 1.5.4 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-12970](https://insights.sbomify.com/CVE-2017-12970/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2006-0144](https://insights.sbomify.com/CVE-2006-0144/): Code injection in n/a (high 7.5)
- [CVE-2017-12971](https://insights.sbomify.com/CVE-2017-12971/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12965 and fix it if it is affected.

What it is: CVE-2017-12965 is a critical authentication bypass vulnerability in n/a, published on 23 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12965 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-2017-12965/ (Markdown: https://insights.sbomify.com/CVE-2017-12965/index.md)
```

## Sources

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

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