Skip to content
Fencer Intel
high 7.4

CVE-2022-31671 json

Harbor fails to validate the user permissions when reading and updating job execution logs through the P2P preheat execution logs

published 4y ago modified 2mo ago also BIT-harbor-2022-31671 , EUVD-2022-6909 , GHSA-q76q-q8hw-hmpw

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

Harbor fails to validate user permissions when reading and updating job execution logs through the P2P preheat execution logs. By sending a request that attempts to read/update P2P preheat execution logs and specifying different job IDs, malicious authenticated users could read all the job logs stored in the Harbor database.

Patch / fix

  • go github.com/goharbor/harbor 1.10.13, 2.4.3, 2.5.2
  • bitnami harbor 2.4.3, 2.5.2
  • linuxfoundation harbor 2.4.3, 2.5.2

Is CVE-2022-31671 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
GitHub 3.1 5.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
NVD 3.1 7.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
OSV 3.1 7.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/goharbor/harbor
>=1.0.0, <1.10.13
>=2.0.0, <2.4.3
>=2.5.0, <2.5.2
1.10.13
2.4.3
2.5.2
bitnami harbor
>=2.0.0, <2.4.3
>=2.5.0, <2.5.2
2.4.3
2.5.2

Affected products

  • n/a Harbor

Classification

Weakness

References

Sources

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.