gsd-2022-38183
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2022-38183", "description": "In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles.", "id": "GSD-2022-38183" }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2022-38183" ], "details": "In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles.", "id": "GSD-2022-38183", "modified": "2023-12-13T01:19:22.365984Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "cve@mitre.org", "ID": "CVE-2022-38183", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "n/a", "version": { "version_data": [ { "version_value": "n/a" } ] } } ] }, "vendor_name": "n/a" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "n/a" } ] } ] }, "references": { "reference_data": [ { "name": "https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/", "refsource": "MISC", "url": "https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/" }, { "name": "https://herolab.usd.de/security-advisories/usd-2022-0015/", "refsource": "MISC", "url": "https://herolab.usd.de/security-advisories/usd-2022-0015/" }, { "name": "GLSA-202210-14", "refsource": "GENTOO", "url": "https://security.gentoo.org/glsa/202210-14" } ] } }, "gitlab.com": { "advisories": [ { "affected_range": "\u003cv1.16.9", "affected_versions": "All versions before 1.16.9", "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "cwe_ids": [ "CWE-1035", "CWE-862", "CWE-937" ], "date": "2023-08-08", "description": "In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles.", "fixed_versions": [ "v1.16.9" ], "identifier": "CVE-2022-38183", "identifiers": [ "CVE-2022-38183" ], "not_impacted": "", "package_slug": "go/github.com/go-gitea/gitea", "pubdate": "2022-08-12", "solution": "Upgrade to version 1.16.9 or above.", "title": "Incorrect Permission Assignment for Critical Resource", "urls": [ "https://nvd.nist.gov/vuln/detail/CVE-2022-38183", "https://herolab.usd.de/security-advisories/usd-2022-0015/", "https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/" ], "uuid": "80f1b804-91ad-4761-a338-325c23c847ec", "versions": [ { "commit": { "sha": "be3da99e8bd4143f724c3639e3766472a09e4ecf", "tags": [ "v1.16.9" ], "timestamp": "20220712182627" }, "number": "v1.16.9" } ] } ] }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "1.16.9", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "cve@mitre.org", "ID": "CVE-2022-38183" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "en", "value": "In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "CWE-732" } ] } ] }, "references": { "reference_data": [ { "name": "https://herolab.usd.de/security-advisories/usd-2022-0015/", "refsource": "MISC", "tags": [ "Broken Link" ], "url": "https://herolab.usd.de/security-advisories/usd-2022-0015/" }, { "name": "https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/", "refsource": "MISC", "tags": [ "Release Notes", "Vendor Advisory" ], "url": "https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/" }, { "name": "GLSA-202210-14", "refsource": "GENTOO", "tags": [ "Third Party Advisory" ], "url": "https://security.gentoo.org/glsa/202210-14" } ] } }, "impact": { "baseMetricV3": { "cvssV3": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.1" }, "exploitabilityScore": 2.8, "impactScore": 3.6 } }, "lastModifiedDate": "2022-11-16T20:01Z", "publishedDate": "2022-08-12T20:15Z" } } }
Loading…
Loading…
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.