CVE-2022-46463 json
An access control issue in Harbor v1.X.X to v2.5.3 allows attackers to access public and private image repositories without authentication.
published 3y ago modified 2mo ago also BIT-harbor-2022-46463 , EUVD-2022-49268
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.4%
- EPSS 6.4% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
An access control issue in Harbor v1.X.X to v2.5.3 allows attackers to access public and private image repositories without authentication. NOTE: the vendor's position is that this "is clearly described in the documentation as a feature."
Patch / fix
- bitnami harbor 2.5.4
Is CVE-2022-46463 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
6.41% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | harbor | >=1.1.0, <2.5.4 |
2.5.4 |
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
github.com
/lanqingaa/123/blob/main/README.md
third-party-advisory, advisory
-
github.com
/lanqingaa/123/tree/bb48caa844d88b0e41e69157f2a2734311abf02d
broken-link, web
-
github.com
/Vad1mo
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-46463
web
Sources
- CVE List CVE-2022-46463
- NVD CVE-2022-46463
- OSV BIT-harbor-2022-46463
Fencer Intel 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.