gsd-2023-26053
Vulnerability from gsd
Modified
2023-12-13 01:20
Details
Gradle is a build tool with a focus on build automation and support for multi-language development. This is a collision attack on long IDs (64bits) for PGP keys. Users of dependency verification in Gradle are vulnerable if they use long IDs for PGP keys in a `trusted-key` or `pgp` element in their dependency verification metadata file. The fix is to fail dependency verification if anything but a fingerprint is used in a trust element in dependency verification metadata. The problem is fixed in Gradle 8.0 and above. The problem is also patched in Gradle 6.9.4 and 7.6.1. As a workaround, use only full fingerprint IDs for `trusted-key` or `pgp` element in the metadata is a protection against this issue.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2023-26053", "id": "GSD-2023-26053", "references": [ "https://www.suse.com/security/cve/CVE-2023-26053.html" ] }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2023-26053" ], "details": "Gradle is a build tool with a focus on build automation and support for multi-language development. This is a collision attack on long IDs (64bits) for PGP keys. Users of dependency verification in Gradle are vulnerable if they use long IDs for PGP keys in a `trusted-key` or `pgp` element in their dependency verification metadata file. The fix is to fail dependency verification if anything but a fingerprint is used in a trust element in dependency verification metadata. The problem is fixed in Gradle 8.0 and above. The problem is also patched in Gradle 6.9.4 and 7.6.1. As a workaround, use only full fingerprint IDs for `trusted-key` or `pgp` element in the metadata is a protection against this issue.", "id": "GSD-2023-26053", "modified": "2023-12-13T01:20:54.178243Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2023-26053", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "gradle", "version": { "version_data": [ { "version_affected": "=", "version_value": "\u003e= 6.2, \u003c 6.9.4" }, { "version_affected": "=", "version_value": "\u003e= 7.0.0, \u003c 7.6.1" } ] } } ] }, "vendor_name": "gradle" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "Gradle is a build tool with a focus on build automation and support for multi-language development. This is a collision attack on long IDs (64bits) for PGP keys. Users of dependency verification in Gradle are vulnerable if they use long IDs for PGP keys in a `trusted-key` or `pgp` element in their dependency verification metadata file. The fix is to fail dependency verification if anything but a fingerprint is used in a trust element in dependency verification metadata. The problem is fixed in Gradle 8.0 and above. The problem is also patched in Gradle 6.9.4 and 7.6.1. As a workaround, use only full fingerprint IDs for `trusted-key` or `pgp` element in the metadata is a protection against this issue." } ] }, "impact": { "cvss": [ { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 6.6, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "HIGH", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H", "version": "3.1" } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "cweId": "CWE-829", "lang": "eng", "value": "CWE-829: Inclusion of Functionality from Untrusted Control Sphere" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/gradle/gradle/security/advisories/GHSA-c724-3xg7-g3hf", "refsource": "MISC", "url": "https://github.com/gradle/gradle/security/advisories/GHSA-c724-3xg7-g3hf" }, { "name": "https://github.com/gradle/gradle/commit/bf3cc0f2b463033037e67aaacda31291643ea1a9", "refsource": "MISC", "url": "https://github.com/gradle/gradle/commit/bf3cc0f2b463033037e67aaacda31291643ea1a9" }, { "name": "https://security.netapp.com/advisory/ntap-20230413-0002/", "refsource": "MISC", "url": "https://security.netapp.com/advisory/ntap-20230413-0002/" } ] }, "source": { "advisory": "GHSA-c724-3xg7-g3hf", "discovery": "UNKNOWN" } }, "gitlab.com": { "advisories": [ { "affected_range": "[6.2.0,6.9.4),[7.0.0,7.6.1)", "affected_versions": "All versions starting from 6.2.0 before 6.9.4, all versions starting from 7.0.0 before 7.6.1", "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "cwe_ids": [ "CWE-1035", "CWE-829", "CWE-937" ], "date": "2023-04-13", "description": "Gradle is a build tool with a focus on build automation and support for multi-language development. This is a collision attack on long IDs (64bits) for PGP keys. Users of dependency verification in Gradle is vulnerable if they use long IDs for PGP keys in a `trusted-key` or `pgp` element in their dependency verification metadata file. The fix is to fail dependency verification if anything but a fingerprint is used in a trust element in dependency verification metadata. The problem is fixed in Gradle 8.0 and above. The problem is also patched in Gradle 6.9.4 and 7.6.1. As a workaround, use only full fingerprint IDs for `trusted-key` or `pgp` element in the metadata is a protection against this issue.", "fixed_versions": [ "6.9.4", "7.6.1" ], "identifier": "CVE-2023-26053", "identifiers": [ "CVE-2023-26053", "GHSA-c724-3xg7-g3hf" ], "not_impacted": "", "package_slug": "maven/org.gradle/gradle-core", "pubdate": "2023-03-02", "solution": "Upgrade to versions 6.9.4, 7.6.1 or above.", "title": "Inclusion of Functionality from Untrusted Control Sphere", "urls": [ "https://nvd.nist.gov/vuln/detail/CVE-2023-26053", "https://github.com/gradle/gradle/commit/bf3cc0f2b463033037e67aaacda31291643ea1a9", "https://github.com/gradle/gradle/security/advisories/GHSA-c724-3xg7-g3hf" ], "uuid": "8abafe67-bf2f-4f59-bb4c-5b800df61746" } ] }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:gradle:gradle:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "6.9.4", "versionStartIncluding": "6.2.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:gradle:gradle:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "7.6.1", "versionStartIncluding": "7.0.0", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2023-26053" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "en", "value": "Gradle is a build tool with a focus on build automation and support for multi-language development. This is a collision attack on long IDs (64bits) for PGP keys. Users of dependency verification in Gradle are vulnerable if they use long IDs for PGP keys in a `trusted-key` or `pgp` element in their dependency verification metadata file. The fix is to fail dependency verification if anything but a fingerprint is used in a trust element in dependency verification metadata. The problem is fixed in Gradle 8.0 and above. The problem is also patched in Gradle 6.9.4 and 7.6.1. As a workaround, use only full fingerprint IDs for `trusted-key` or `pgp` element in the metadata is a protection against this issue." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "CWE-829" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/gradle/gradle/commit/bf3cc0f2b463033037e67aaacda31291643ea1a9", "refsource": "MISC", "tags": [ "Patch" ], "url": "https://github.com/gradle/gradle/commit/bf3cc0f2b463033037e67aaacda31291643ea1a9" }, { "name": "https://github.com/gradle/gradle/security/advisories/GHSA-c724-3xg7-g3hf", "refsource": "MISC", "tags": [ "Vendor Advisory" ], "url": "https://github.com/gradle/gradle/security/advisories/GHSA-c724-3xg7-g3hf" }, { "name": "https://security.netapp.com/advisory/ntap-20230413-0002/", "refsource": "MISC", "tags": [], "url": "https://security.netapp.com/advisory/ntap-20230413-0002/" } ] } }, "impact": { "baseMetricV3": { "cvssV3": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 9.8, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1" }, "exploitabilityScore": 3.9, "impactScore": 5.9 } }, "lastModifiedDate": "2023-04-13T17:15Z", "publishedDate": "2023-03-02T04: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.