gsd-2021-29481
Vulnerability from gsd
Modified
2023-12-13 01:23
Details
Ratpack is a toolkit for creating web applications. In versions prior to 1.9.0, the default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies. For this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies. As of version 1.9.0, a securely randomly generated signing key is used. As a workaround, one may supply an encryption key, as per the documentation recommendation.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2021-29481", "description": "Ratpack is a toolkit for creating web applications. In versions prior to 1.9.0, the default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies. For this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies. As of version 1.9.0, a securely randomly generated signing key is used. As a workaround, one may supply an encryption key, as per the documentation recommendation.", "id": "GSD-2021-29481" }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2021-29481" ], "details": "Ratpack is a toolkit for creating web applications. In versions prior to 1.9.0, the default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies. For this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies. As of version 1.9.0, a securely randomly generated signing key is used. As a workaround, one may supply an encryption key, as per the documentation recommendation.", "id": "GSD-2021-29481", "modified": "2023-12-13T01:23:36.470348Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2021-29481", "STATE": "PUBLIC", "TITLE": "Client side sessions should not allow unencrypted storage" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "ratpack", "version": { "version_data": [ { "version_value": "\u003c 1.9.0" } ] } } ] }, "vendor_name": "ratpack" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "Ratpack is a toolkit for creating web applications. In versions prior to 1.9.0, the default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies. For this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies. As of version 1.9.0, a securely randomly generated signing key is used. As a workaround, one may supply an encryption key, as per the documentation recommendation." } ] }, "impact": { "cvss": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", "version": "3.1" } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "CWE-312: Cleartext Storage of Sensitive Information" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/ratpack/ratpack/security/advisories/GHSA-phj8-4cq3-794g", "refsource": "CONFIRM", "url": "https://github.com/ratpack/ratpack/security/advisories/GHSA-phj8-4cq3-794g" }, { "name": "https://github.com/ratpack/ratpack/pull/1590", "refsource": "MISC", "url": "https://github.com/ratpack/ratpack/pull/1590" } ] }, "source": { "advisory": "GHSA-phj8-4cq3-794g", "discovery": "UNKNOWN" } }, "gitlab.com": { "advisories": [ { "affected_range": "(,1.9.0)", "affected_versions": "All versions before 1.9.0", "cvss_v2": "AV:N/AC:L/Au:N/C:P/I:N/A:N", "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "cwe_ids": [ "CWE-1035", "CWE-312", "CWE-937" ], "date": "2021-07-07", "description": "Ratpack is a toolkit for creating web applications., the default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies. For this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies. As of, a securely randomly generated signing key is used. As a workaround, one may supply an encryption key, as per the documentation recommendation.", "fixed_versions": [ "1.9.0" ], "identifier": "CVE-2021-29481", "identifiers": [ "CVE-2021-29481", "GHSA-phj8-4cq3-794g" ], "not_impacted": "All versions starting from 1.9.0", "package_slug": "maven/io.ratpack/ratpack-core", "pubdate": "2021-06-29", "solution": "Upgrade to version 1.9.0 or above.", "title": "Cleartext Storage of Sensitive Information", "urls": [ "https://nvd.nist.gov/vuln/detail/CVE-2021-29481" ], "uuid": "6bc9a9f3-c733-49c9-938e-2bb9f93217ca" }, { "affected_range": "(,1.9.0)", "affected_versions": "All versions before 1.9.0", "cvss_v2": "AV:N/AC:L/Au:N/C:P/I:N/A:N", "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "cwe_ids": [ "CWE-1035", "CWE-312", "CWE-79", "CWE-937" ], "date": "2021-09-01", "description": "Ratpack is a toolkit for creating web applications. In versions prior to 1.9.0, the default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies. For this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies. As of version 1.9.0, a securely randomly generated signing key is used. As a workaround, one may supply an encryption key, as per the documentation recommendation.", "fixed_versions": [ "1.9.0" ], "identifier": "CVE-2021-29481", "identifiers": [ "GHSA-phj8-4cq3-794g", "CVE-2021-29481" ], "not_impacted": "All versions starting from 1.9.0", "package_slug": "maven/io.ratpack/ratpack-session", "pubdate": "2021-07-01", "solution": "Upgrade to version 1.9.0 or above.", "title": "Cleartext Storage of Sensitive Information", "urls": [ "https://github.com/ratpack/ratpack/security/advisories/GHSA-phj8-4cq3-794g", "https://nvd.nist.gov/vuln/detail/CVE-2021-29481", "https://github.com/ratpack/ratpack/pull/1590", "https://github.com/advisories/GHSA-phj8-4cq3-794g" ], "uuid": "01f124f8-bf2c-4b02-ab03-c07124859690" } ] }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:ratpack_project:ratpack:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "1.9.0", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2021-29481" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "en", "value": "Ratpack is a toolkit for creating web applications. In versions prior to 1.9.0, the default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies. For this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies. As of version 1.9.0, a securely randomly generated signing key is used. As a workaround, one may supply an encryption key, as per the documentation recommendation." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "CWE-312" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/ratpack/ratpack/pull/1590", "refsource": "MISC", "tags": [ "Patch", "Third Party Advisory" ], "url": "https://github.com/ratpack/ratpack/pull/1590" }, { "name": "https://github.com/ratpack/ratpack/security/advisories/GHSA-phj8-4cq3-794g", "refsource": "CONFIRM", "tags": [ "Third Party Advisory" ], "url": "https://github.com/ratpack/ratpack/security/advisories/GHSA-phj8-4cq3-794g" } ] } }, "impact": { "baseMetricV2": { "acInsufInfo": false, "cvssV2": { "accessComplexity": "LOW", "accessVector": "NETWORK", "authentication": "NONE", "availabilityImpact": "NONE", "baseScore": 5.0, "confidentialityImpact": "PARTIAL", "integrityImpact": "NONE", "vectorString": "AV:N/AC:L/Au:N/C:P/I:N/A:N", "version": "2.0" }, "exploitabilityScore": 10.0, "impactScore": 2.9, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "severity": "MEDIUM", "userInteractionRequired": false }, "baseMetricV3": { "cvssV3": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "version": "3.1" }, "exploitabilityScore": 3.9, "impactScore": 3.6 } }, "lastModifiedDate": "2021-07-07T16:44Z", "publishedDate": "2021-06-29T19: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.
Loading…
Loading…