# CVE-2023-41881: Deleting a collaboration should also delete linked resources


- **Severity:** Low 3.7 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Oct 2023
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rf54-7qrr-96j6, PYSEC-2023-200

## What is CVE-2023-41881?

CVE-2023-41881 is a low-severity vulnerability in vantage6, published on 11 Oct 2023. 

### Official description

vantage6 is privacy preserving federated learning infrastructure. When a collaboration is deleted, the linked resources (such as tasks from that collaboration) should be deleted. This is partly to manage data properly, but also to prevent a potential (but unlikely) side-effect that affects versions prior to 4.0.0, where if a collaboration with id=10 is deleted, and subsequently a new collaboration is created with id=10, the authenticated users in that collaboration could potentially see results of the deleted collaboration in some cases. Version 4.0.0 contains a patch for this issue. There are no known workarounds.

Weakness: CWE-708 (Incorrect Ownership Assignment), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-41881?

3 open source packages ship an affected version, including vantage6. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vantage6` | PyPI | All versions | 4.0.0 |
| `vantage6` | PyPI | All versions | 4.0.0 |
| `vantage6` | PyPI | All versions | 4.0.0 |

Products: Vantage6 Vantage6.

## How do I fix CVE-2023-41881?

Upgrade vantage6 to 4.0.0 or later.

## Is CVE-2023-41881 being exploited?

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

## Other vulnerabilities in vantage6

- [CVE-2024-21649](https://insights.sbomify.com/CVE-2024-21649/): Remote code execution (high 8.8)
- [CVE-2023-23929](https://insights.sbomify.com/CVE-2023-23929/): Refresh tokens do not expire in Vantage6 (high 8.8)
- [CVE-2023-47631](https://insights.sbomify.com/CVE-2023-47631/): vantage6 Node accepts non-whitelisted algorithms from malicious server (high 7.2)
- [CVE-2024-21653](https://insights.sbomify.com/CVE-2024-21653/): vantage6 insecure SSH configuration for node and server containers (medium 6.5)
- [CVE-2023-22738](https://insights.sbomify.com/CVE-2023-22738/): Improper Preservation of Permissions in vantage6 (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41881 and fix it if it is affected.

What it is: CVE-2023-41881 is a low-severity vulnerability in vantage6, published on 11 Oct 2023. 
Exploitation: There is no known exploitation of CVE-2023-41881 in the wild and no public exploit code.

Affected packages and fixed versions:
- vantage6 (PyPI): affected all versions; fixed in 4.0.0
- vantage6 (PyPI): affected all versions; fixed in 4.0.0
- vantage6 (PyPI): affected all versions; fixed in 4.0.0

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

## Sources

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

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