ghsa-q76q-q8hw-hmpw
Vulnerability from github
Impact
Harbor fails to validate the user permissions when reading job execution logs through the P2P preheat execution logs - API call
GET /projects/{project_name}/preheat/policies/{preheat_policy_name}/executions/{execution_id}/tasks/{task_id}/logs
By sending a request that attempts to read P2P preheat execution logs and specifying different job ids, malicious authenticatedusers could read all the job logs stored in the Harbor database.
Patches
This and similar issues are fixed in Harbor v2.5.2 and later. Please upgrade as soon as possible.
Workarounds
There are no workarounds available.
For more information
If you have any questions or comments about this advisory: * Open an issue in the Harbor GitHub repository
Credits
Thanks to Gal Goldstein and Daniel Abeles from Oxeye Security for reporting this issue.
{ "affected": [ { "database_specific": { "last_known_affected_version_range": "\u003c= 1.10.12" }, "package": { "ecosystem": "Go", "name": "github.com/goharbor/harbor" }, "ranges": [ { "events": [ { "introduced": "1.0.0" }, { "fixed": "1.10.13" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c= 2.4.2" }, "package": { "ecosystem": "Go", "name": "github.com/goharbor/harbor" }, "ranges": [ { "events": [ { "introduced": "2.0.0" }, { "fixed": "2.4.3" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c= 2.5.1" }, "package": { "ecosystem": "Go", "name": "github.com/goharbor/harbor" }, "ranges": [ { "events": [ { "introduced": "2.5.0" }, { "fixed": "2.5.2" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2022-31671" ], "database_specific": { "cwe_ids": [ "CWE-285" ], "github_reviewed": true, "github_reviewed_at": "2022-09-09T19:47:03Z", "nvd_published_at": "2024-11-14T12:15:17Z", "severity": "MODERATE" }, "details": "### Impact\nHarbor fails to validate the user permissions when reading job execution logs through the P2P preheat execution logs - API call\n\n\u00a0 GET /projects/{project_name}/preheat/policies/{preheat_policy_name}/executions/{execution_id}/tasks/{task_id}/logs\n\nBy sending a request that attempts to read P2P preheat execution logs and specifying different job ids, malicious authenticatedusers could read all the job logs stored in the Harbor database.\n\n### Patches\nThis and similar issues are fixed in Harbor v2.5.2 and later. Please upgrade as soon as possible.\n\n### Workarounds\nThere are no workarounds available.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Harbor GitHub repository](https://github.com/goharbor/harbor)\n\n### Credits\nThanks to [Gal Goldstein](https://www.linkedin.com/in/gal-goldshtein/) and [Daniel Abeles](https://www.linkedin.com/in/daniel-abeles/) from [Oxeye Security](https://www.oxeye.io/) for reporting this issue.\n", "id": "GHSA-q76q-q8hw-hmpw", "modified": "2024-11-14T17:53:27Z", "published": "2022-09-09T19:47:03Z", "references": [ { "type": "WEB", "url": "https://github.com/goharbor/harbor/security/advisories/GHSA-3wpx-625q-22j7" }, { "type": "WEB", "url": "https://github.com/goharbor/harbor/security/advisories/GHSA-q76q-q8hw-hmpw" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31671" }, { "type": "PACKAGE", "url": "https://github.com/goharbor/harbor" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N", "type": "CVSS_V3" } ], "summary": "Harbor fails to validate the user permissions when reading job execution logs through the P2P preheat execution logs" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.