Skip to content
Noroxi
NVD / CVE Program· CNA vmware

CVE-2022-31666: Harbor fails to validate user permissions while Viewing, updating and deleting Webhook policies

MediumCVSS 5.4 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.49% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: github.com/goharbor/harbor (Go) 1.10.13, 2.4.3, 2.5.2.
  • Severity is disputed: the assigning authority (CNA) scores it 7.7, NVD 5.4.

Low priority for now. Upgrade to github.com/goharbor/harbor (Go) 1.10.13, 2.4.3, 2.5.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Harbor fails to validate user permissions while deleting Webhook policies, allowing malicious users to view, update and delete Webhook policies of other users.  The attacker could modify Webhook policies configured in other projects.

Published
Nov 14, 2024
Updated
Jun 17, 2026
EPSS
0.4% · 42th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.4
CNA · vmware
7.7
2.3 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-31666

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linuxfoundation records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxfoundationharbor

Versions reported by the vendor

Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a Harbor

    • Harbor 2.x<=2.4.2; 2.5<=2.5.1affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linuxfoundation harbor2.0.0 and later · before 2.4.3
  • linuxfoundation harbor2.5.0 and later · before 2.5.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/goharbor/harborfrom 1.0.0 · before 1.10.131.10.13
Gogithub.com/goharbor/harborfrom 2.0.0 · before 2.4.32.4.3
Gogithub.com/goharbor/harborfrom 2.5.0 · before 2.5.22.5.2

Same product

linuxfoundation: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-4404Use of hard coded credentials in GoHarbor Harbor
    37Monitor
  • CVE-2019-19023Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 has a Privilege Escalation Vulnerability in the VMware Harbor Container…
    35Monitor
  • CVE-2017-17697The Ping() function in ui/api/target.go in Harbor through 1.3.0-rc4 has SSRF via the endpoint parameter to /api/targets/ping.
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-22261Jun 10, 2024 · SQL Injection in Harbor scan log API
    22Monitor
  • ← EarlierCVE-2024-22278Aug 1, 2024 · Harbor fails to validate the user permissions when updating project configurations
    17Monitor
  • Later →CVE-2022-31667Nov 14, 2024 · Harbor fails to validate the user permissions when updating a robot account
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/goharbor/harbor1.10.13Package registry (OSV)
Go:github.com/goharbor/harbor2.4.3Package registry (OSV)
Go:github.com/goharbor/harbor2.5.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2022-316680 days apartUser permission validation failure and disclosure of P2P preheat execution logs
    30Monitor
  • CVE-2022-316690 days apartHarbor fails to validate the user permissions when updating tag immutability policies
    30Monitor
  • CVE-2022-316700 days apartHarbor fails to validate the user permissions when updating tag retention policies
    30Monitor
  • CVE-2022-316710 days apartHarbor fails to validate the user permissions when reading and updating job execution logs through the P2P preheat execution logs
    29Monitor
  • CVE-2022-316670 days apartHarbor fails to validate the user permissions when updating a robot account
    25Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-285 · Improper Authorization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records