# CVE-2017-15055: TeamPass Improper Privilege Management

> An authenticated attacker can bypass access controls to read, modify, or delete arbitrary password items and directory attributes in TeamPass.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** Yes
- **Published:** 27 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7ghm-6p42-h226

## What is CVE-2017-15055?

CVE-2017-15055 is a high-severity missing authorization vulnerability in Teampass Teampass, published on 27 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TeamPass before 2.1.27.9 does not properly enforce item access control when requesting items.queries.php. It is then possible to copy any arbitrary item into a directory controlled by the attacker, edit any item within a read-only directory, delete an arbitrary item, delete the file attachments of an arbitrary item, copy the password of an arbitrary item to the copy/paste buffer, access the history of an arbitrary item, and edit attributes of an arbitrary directory. To exploit the vulnerability, an authenticated attacker must tamper with the requests sent directly, for example by changing the "item_id" parameter when invoking "copy_item" on items.queries.php.

Weakness: CWE-269 (Improper Privilege Management)

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

2 open source packages ship an affected version, including nilsteampassnet/teampass. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nilsteampassnet/teampass` | Packagist | All versions | 2.1.27.9 |
| `nilsteampassnet/teampass` | Packagist | All versions | 2.1.27.9 |

Products: Teampass Teampass.

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

Upgrade nilsteampassnet/teampass to 2.1.27.9 or later.

## Is CVE-2017-15055 being exploited?

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

## Other vulnerabilities in Teampass Teampass

- [CVE-2019-1000001](https://insights.sbomify.com/CVE-2019-1000001/): TeamPass Storing Passwords in a Recoverable Format vulnerability (critical 9.8)
- [CVE-2017-9436](https://insights.sbomify.com/CVE-2017-9436/): TeamPass SQL injection in users.queries.php (critical 9.8)
- [CVE-2015-7564](https://insights.sbomify.com/CVE-2015-7564/): TeamPass vulnerable to SQL Injection (critical 9.8)
- [CVE-2026-3106](https://insights.sbomify.com/CVE-2026-3106/): Multiple vulnerabilities in Teampass (critical 9.3)
- [CVE-2026-3107](https://insights.sbomify.com/CVE-2026-3107/): Multiple vulnerabilities in Teampass (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15055 is a high-severity missing authorization vulnerability in Teampass Teampass, published on 27 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-15055 in the wild and no public exploit code.

Affected packages and fixed versions:
- nilsteampassnet/teampass (Packagist): affected all versions; fixed in 2.1.27.9
- nilsteampassnet/teampass (Packagist): affected all versions; fixed in 2.1.27.9

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

## Sources

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

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