# CVE-2017-1000150: Security feature bypass in n/a

> Attackers can hijack user sessions via session fixation because Mahara fails to regenerate session IDs on login or logout.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 3 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j2wq-fwmf-pw74

## What is CVE-2017-1000150?

CVE-2017-1000150 is a high-severity vulnerability in Mahara Mahara, published on 3 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mahara 15.04 before 15.04.7 and 15.10 before 15.10.3 are vulnerable to prevent session IDs from being regenerated on login or logout. This makes users of the site more vulnerable to session fixation attacks.

Weakness: CWE-384 (Session Fixation)

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

It affects 1 product.


Products: Mahara Mahara.

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

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

## Is CVE-2017-1000150 being exploited?

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

## Other vulnerabilities in Mahara Mahara

- [CVE-2022-45134](https://insights.sbomify.com/CVE-2022-45134/): Deserialization in n/a (critical 9.8)
- [CVE-2022-44544](https://insights.sbomify.com/CVE-2022-44544/): Command injection in n/a (critical 9.8)
- [CVE-2021-40849](https://insights.sbomify.com/CVE-2021-40849/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-1000152](https://insights.sbomify.com/CVE-2017-1000152/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-1000153](https://insights.sbomify.com/CVE-2017-1000153/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000150 is a high-severity vulnerability in Mahara Mahara, published on 3 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1000150 in the wild and no public exploit code.

Affected product: Mahara Mahara. 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-1000150/ (Markdown: https://insights.sbomify.com/CVE-2017-1000150/index.md)
```

## Sources

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

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