GSD-2023-27539
Vulnerability from gsd - Updated: 2023-03-13 00:00Details
There is a denial of service vulnerability in the header parsing component of Rack. This vulnerability has been assigned the CVE identifier CVE-2023-27539.
Versions Affected: >= 2.0.0 Not affected: None. Fixed Versions: 2.2.6.4, 3.0.6.1
# Impact
Carefully crafted input can cause header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that parse headers using Rack (virtually all Rails applications) are impacted.
# Workarounds
Setting Regexp.timeout in Ruby 3.2 is a possible workaround.
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2023-27539",
"id": "GSD-2023-27539"
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"affected": [
{
"package": {
"ecosystem": "RubyGems",
"name": "rack",
"purl": "pkg:gem/rack"
}
}
],
"aliases": [
"CVE-2023-27539",
"GHSA-c6qg-cjj8-47qp"
],
"details": "There is a denial of service vulnerability in the header parsing component of Rack. This vulnerability has been assigned the CVE identifier CVE-2023-27539.\n\nVersions Affected: \u003e= 2.0.0 Not affected: None. Fixed Versions: 2.2.6.4, 3.0.6.1\n\n# Impact\nCarefully crafted input can cause header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that parse headers using Rack (virtually all Rails applications) are impacted.\n\n# Workarounds\nSetting Regexp.timeout in Ruby 3.2 is a possible workaround.\n",
"id": "GSD-2023-27539",
"modified": "2023-03-13T00:00:00.000Z",
"published": "2023-03-13T00:00:00.000Z",
"references": [
{
"type": "WEB",
"url": "https://discuss.rubyonrails.org/t/cve-2023-27539-possible-denial-of-service-vulnerability-in-racks-header-parsing/82466"
}
],
"schema_version": "1.4.0",
"summary": "Possible Denial of Service Vulnerability in Rack\u2019s header parsing"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2023-27539",
"STATE": "RESERVED"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided."
}
]
}
},
"github.com/rubysec/ruby-advisory-db": {
"cve": "2023-27539",
"date": "2023-03-13",
"description": "There is a denial of service vulnerability in the header parsing component of Rack. This vulnerability has been assigned the CVE identifier CVE-2023-27539.\n\nVersions Affected: \u003e= 2.0.0 Not affected: None. Fixed Versions: 2.2.6.4, 3.0.6.1\n\n# Impact\nCarefully crafted input can cause header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that parse headers using Rack (virtually all Rails applications) are impacted.\n\n# Workarounds\nSetting Regexp.timeout in Ruby 3.2 is a possible workaround.\n",
"gem": "rack",
"ghsa": "c6qg-cjj8-47qp",
"patched_versions": [
"~\u003e 2.0, \u003e= 2.2.6.4",
"\u003e= 3.0.6.1"
],
"title": "Possible Denial of Service Vulnerability in Rack\u2019s header parsing",
"url": "https://discuss.rubyonrails.org/t/cve-2023-27539-possible-denial-of-service-vulnerability-in-racks-header-parsing/82466"
},
"gitlab.com": {
"advisories": [
{
"affected_range": "\u003e=2.0.0 \u003c2.2.6.4||\u003e=3.0.0 \u003c3.0.6.1",
"affected_versions": "All versions starting from 2.0.0 before 2.2.6.4, all versions starting from 3.0.0 before 3.0.6.1",
"cwe_ids": [
"CWE-1035",
"CWE-937"
],
"date": "2023-03-15",
"description": "There is a denial of service vulnerability in the header parsing component of Rack. Carefully crafted input can cause header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that parse headers using Rack (virtually all Rails applications) are impacted. Workarounds Setting `Regexp.timeout` in Ruby 3.2 is a possible workaround.",
"fixed_versions": [
"2.2.6.4",
"3.0.6.1"
],
"identifier": "GMS-2023-769",
"identifiers": [
"GHSA-c6qg-cjj8-47qp",
"GMS-2023-769",
"CVE-2023-27539"
],
"not_impacted": "All versions before 2.0.0, all versions starting from 2.2.6.4 before 3.0.0, all versions starting from 3.0.6.1",
"package_slug": "gem/rack",
"pubdate": "2023-03-15",
"solution": "Upgrade to versions 2.2.6.4, 3.0.6.1 or above.",
"title": "Possible Denial of Service Vulnerability in Rack\u2019s header parsing",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2023-27539",
"https://discuss.rubyonrails.org/t/cve-2023-27539-possible-denial-of-service-vulnerability-in-racks-header-parsing/82466",
"https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2023-27539.yml",
"https://github.com/advisories/GHSA-c6qg-cjj8-47qp"
],
"uuid": "3a275b96-84c7-4c7c-8017-b7fd82af8c53"
}
]
}
}
}
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.