gsd-2019-25025
Vulnerability from gsd
Modified
2021-03-08 00:00
Details
The `activerecord-session_store` (aka Active Record Session Store) component
through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering
information about whether a guessed session ID is valid. Consequently, remote attackers
can leverage timing discrepancies to achieve a correct guess in a relatively short
amount of time. This is a related issue to CVE-2019-16782.
## Recommendation
Users should upgrade to `activerecord-session_store` version 2.0.0 or later.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2019-25025", "description": "The activerecord-session_store (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.", "id": "GSD-2019-25025", "references": [ "https://www.suse.com/security/cve/CVE-2019-25025.html", "https://access.redhat.com/errata/RHSA-2021:4702" ] }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "affected": [ { "package": { "ecosystem": "RubyGems", "name": "activerecord-session_store", "purl": "pkg:gem/activerecord-session_store" } } ], "aliases": [ "CVE-2019-25025", "GHSA-cvw2-xj8r-mjf7" ], "details": "The `activerecord-session_store` (aka Active Record Session Store) component\nthrough 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering\ninformation about whether a guessed session ID is valid. Consequently, remote attackers\ncan leverage timing discrepancies to achieve a correct guess in a relatively short\namount of time. This is a related issue to CVE-2019-16782.\n\n## Recommendation\nUsers should upgrade to `activerecord-session_store` version 2.0.0 or later.\n", "id": "GSD-2019-25025", "modified": "2021-03-08T00:00:00.000Z", "published": "2021-03-08T00:00:00.000Z", "references": [ { "type": "WEB", "url": "https://github.com/advisories/GHSA-cvw2-xj8r-mjf7" }, { "type": "WEB", "url": "https://github.com/rails/activerecord-session_store/pull/151" }, { "type": "WEB", "url": "https://github.com/rails/activerecord-session_store/releases/tag/v2.0.0" } ], "related": [ "CVE-2019-16782" ], "schema_version": "1.4.0", "severity": [ { "score": 5.9, "type": "CVSS_V3" } ], "summary": "activerecord-session_store Timing Attack" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "cve@mitre.org", "ID": "CVE-2019-25025", "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": "The activerecord-session_store (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "n/a" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/rails/activerecord-session_store/pull/151", "refsource": "MISC", "url": "https://github.com/rails/activerecord-session_store/pull/151" } ] } }, "github.com/rubysec/ruby-advisory-db": { "cve": "2019-25025", "cvss_v3": 5.9, "date": "2021-03-08", "description": "The `activerecord-session_store` (aka Active Record Session Store) component\nthrough 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering\ninformation about whether a guessed session ID is valid. Consequently, remote attackers\ncan leverage timing discrepancies to achieve a correct guess in a relatively short\namount of time. This is a related issue to CVE-2019-16782.\n\n## Recommendation\nUsers should upgrade to `activerecord-session_store` version 2.0.0 or later.\n", "gem": "activerecord-session_store", "ghsa": "cvw2-xj8r-mjf7", "patched_versions": [ "\u003e= 2.0.0" ], "related": { "cve": [ "2019-16782" ], "url": [ "https://github.com/rails/activerecord-session_store/pull/151", "https://github.com/rails/activerecord-session_store/releases/tag/v2.0.0" ] }, "title": "activerecord-session_store Timing Attack", "url": "https://github.com/advisories/GHSA-cvw2-xj8r-mjf7" }, "gitlab.com": { "advisories": [ { "affected_range": "\u003c=1.1.3", "affected_versions": "All versions up to 1.1.3", "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:L/I:N/A:N", "cwe_ids": [ "CWE-1035", "CWE-937", "CWE-208" ], "date": "2021-03-15", "description": "The activerecord-session_store (aka Active Record Session Store) component for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.", "fixed_versions": [ "2.0.0" ], "identifier": "CVE-2019-25025", "identifiers": [ "CVE-2019-25025" ], "not_impacted": "All versions after 1.1.3", "package_slug": "gem/activerecord-session_store", "pubdate": "2021-03-05", "solution": "Upgrade to version 2.0.0 or above.", "title": "Observable Timing Discrepancy", "urls": [ "https://nvd.nist.gov/vuln/detail/CVE-2019-25025", "https://github.com/rails/activerecord-session_store/pull/151" ], "uuid": "272afa2d-2b22-4983-a2fb-61dc4fa86a6a" } ] }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:rubyonrails:active_record_session_store:*:*:*:*:*:ruby_on_rails:*:*", "cpe_name": [], "versionEndIncluding": "1.1.3", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "cve@mitre.org", "ID": "CVE-2019-25025" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "en", "value": "The activerecord-session_store (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "NVD-CWE-Other" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/rails/activerecord-session_store/pull/151", "refsource": "MISC", "tags": [ "Patch", "Third Party Advisory" ], "url": "https://github.com/rails/activerecord-session_store/pull/151" } ] } }, "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": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "version": "3.1" }, "exploitabilityScore": 3.9, "impactScore": 1.4 } }, "lastModifiedDate": "2021-03-15T16:44Z", "publishedDate": "2021-03-05T06:15Z" } } }
Loading...
Loading...
- 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.