# CVE-2009-2171: Missing authorization in n/a

> Remote authenticated users can read other users' artefacts due to missing permission checks when saving views.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **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:** 23 Jun 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7prf-5qjr-qmp5

## What is CVE-2009-2171?

CVE-2009-2171 is a medium-severity missing authorization vulnerability in Mahara Mahara, published on 23 Jun 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mahara 1.1 before 1.1.5 does not apply permission checks when saving a view that contains artefacts, which allows remote authenticated users to read another user's artefact.

Weakness: CWE-264

## Which versions are affected by CVE-2009-2171?

It affects 1 product.


Products: Mahara Mahara.

## How do I fix CVE-2009-2171?

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

## Is CVE-2009-2171 being exploited?

There is no known exploitation of CVE-2009-2171 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-2009-2171 and fix it if it is affected.

What it is: CVE-2009-2171 is a medium-severity missing authorization vulnerability in Mahara Mahara, published on 23 Jun 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-2171 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-2009-2171/ (Markdown: https://insights.sbomify.com/CVE-2009-2171/index.md)
```

## Sources

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

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