CVE-2023-41881 json
Deleting a collaboration should also delete linked resources
published 2023-10-11 3 y ago modified 2026-09-10 1 mo ago also GHSA-rf54-7qrr-96j6 , PYSEC-2023-200 , EUVD-2023-0258
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi vantage6 4.0.0
- vantage6 vantage6 4.0.0
- github.com/vantage6/vantage6@cce9538 commit
- github.com/vantage6/vantage6#748 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.7 | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | vantage6 | <4.0.0 |
4.0.0 |
Affected products
- vantage6 vantage6
Classification
References
-
github.com
/vantage6/vantage6/pull/748
web, patch
-
github.com
/vantage6/vantage6/commit/cce9538f8b70e814c080dd0ae43b297f3af8a732
web
-
github.com
/vantage6/vantage6/security/advisories/GHSA-rf54-7qrr-96j6
web, third-party-advisory, advisory
-
github.com
/vantage6/vantage6/blob/0682c4288f43fee5bcc72dc448cdd99bd7e57f76/docs/release_notes.rst#400
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2023-41881
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/vantage6/PYSEC-2023-200.yaml
web
-
github.com
/vantage6/vantage6
package
Sources
- CVE List CVE-2023-41881
- GitHub Advisory GHSA-rf54-7qrr-96j6
- NVD CVE-2023-41881
- OSV PYSEC-2023-200
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.