CVSS 3.1
5.5 mediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:NMedium (5.5) in linuxfoundation harbor. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/goharbor/harbor 2.10.2, 2.10.2+incompatible, 2.8.6.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:Ngithub.com/goharbor/harbor (Go): fixed in 2.8.6, 2.9.4, 2.10.2, 2.8.6+incompatible, 2.9.4+incompatible, 2.10.2+incompatibleExplain CVE-2024-22261 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-22261?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-22261?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-22261 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Harbor | from 2.8.1 through 2.8.5 |
| Harbor | from 2.9.0 through 2.9.3 |
| Harbor | from 2.10.0 through 2.10.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-vw63-824v-qf2j | Go | github.com/goharbor/harbor | <2.8.6 | 2.8.6 |
| GHSA-vw63-824v-qf2j | Go | github.com/goharbor/harbor | >=2.9.0 <2.9.4 | 2.9.4 |
| GHSA-vw63-824v-qf2j | Go | github.com/goharbor/harbor | >=2.10.0 <2.10.2 | 2.10.2 |
| GO-2024-2916 | Go | github.com/goharbor/harbor | <2.8.6+incompatible >=2.9.0+incompatible <2.9.4+incompatible >=2.10.0+incompatible <2.10.2+incompatible | 2.8.6+incompatible, 2.9.4+incompatible, 2.10.2+incompatible |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.