GSD-2019-25025
Vulnerability from gsd - Updated: 2021-03-08 00:00Details
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…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.