GSD-2023-28859
Vulnerability from gsd - Updated: 2023-12-13 01:20Details
redis-py before 4.4.4 and 4.5.x before 4.5.4 leaves a connection open after canceling an async Redis command at an inopportune time, and can send response data to the client of an unrelated request. (This could, for example, happen for a non-pipeline operation.) NOTE: the solutions for CVE-2023-28859 address data leakage across AsyncIO connections in general.
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2023-28859",
"id": "GSD-2023-28859"
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"aliases": [
"CVE-2023-28859"
],
"details": "redis-py before 4.4.4 and 4.5.x before 4.5.4 leaves a connection open after canceling an async Redis command at an inopportune time, and can send response data to the client of an unrelated request. (This could, for example, happen for a non-pipeline operation.) NOTE: the solutions for CVE-2023-28859 address data leakage across AsyncIO connections in general.",
"id": "GSD-2023-28859",
"modified": "2023-12-13T01:20:48.955986Z",
"schema_version": "1.4.0"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2023-28859",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "n/a",
"version": {
"version_data": [
{
"version_value": "not down converted",
"x_cve_json_5_version_data": {
"versions": [
{
"status": "unknown",
"version": "n/a"
}
]
}
}
]
}
}
]
},
"vendor_name": "n/a"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "redis-py before 4.4.4 and 4.5.x before 4.5.4 leaves a connection open after canceling an async Redis command at an inopportune time, and can send response data to the client of an unrelated request. (This could, for example, happen for a non-pipeline operation.) NOTE: the solutions for CVE-2023-28859 address data leakage across AsyncIO connections in general."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "n/a"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/redis/redis-py/pull/2641",
"refsource": "MISC",
"url": "https://github.com/redis/redis-py/pull/2641"
},
{
"name": "https://github.com/redis/redis-py/issues/2665",
"refsource": "MISC",
"url": "https://github.com/redis/redis-py/issues/2665"
},
{
"name": "https://github.com/redis/redis-py/releases/tag/v4.4.4",
"refsource": "MISC",
"url": "https://github.com/redis/redis-py/releases/tag/v4.4.4"
},
{
"name": "https://github.com/redis/redis-py/releases/tag/v4.5.4",
"refsource": "MISC",
"url": "https://github.com/redis/redis-py/releases/tag/v4.5.4"
},
{
"name": "https://github.com/redis/redis-py/pull/2666",
"refsource": "MISC",
"url": "https://github.com/redis/redis-py/pull/2666"
}
]
}
},
"gitlab.com": {
"advisories": [
{
"affected_range": "\u003e=4.2.0,\u003c4.4.4||\u003e=4.5.0,\u003c4.5.4",
"affected_versions": "All versions starting from 4.2.0 before 4.4.4, all versions starting from 4.5.0 before 4.5.4",
"cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"cwe_ids": [
"CWE-1035",
"CWE-459",
"CWE-937"
],
"date": "2023-05-17",
"description": "redis-py through 4.5.3 leaves a connection open after canceling an async Redis command at an inopportune time (in the case of a non-pipeline operation), and can send response data to the client of an unrelated request. NOTE: this issue exists because of an incomplete fix for CVE-2023-28858.",
"fixed_versions": [
"4.4.4",
"4.5.4"
],
"identifier": "CVE-2023-28859",
"identifiers": [
"CVE-2023-28859",
"GHSA-8fww-64cx-x8p5"
],
"not_impacted": "All versions before 4.2.0, all versions starting from 4.4.4 before 4.5.0, all versions starting from 4.5.4",
"package_slug": "pypi/redis",
"pubdate": "2023-03-26",
"solution": "Upgrade to versions 4.4.4, 4.5.4 or above.",
"title": "redis-py Race Condition due to incomplete fix",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2023-28859",
"https://github.com/redis/redis-py/issues/2665",
"https://github.com/redis/redis-py/pull/2641",
"https://github.com/advisories/GHSA-8fww-64cx-x8p5"
],
"uuid": "807ee8a6-3fd2-4e47-a65e-ae0f0e1e89bd"
}
]
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:redis:redis-py:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "4.5.4",
"versionStartIncluding": "4.5.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:redis:redis-py:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "4.4.4",
"versionStartIncluding": "4.2.0",
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2023-28859"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "en",
"value": "redis-py before 4.4.4 and 4.5.x before 4.5.4 leaves a connection open after canceling an async Redis command at an inopportune time, and can send response data to the client of an unrelated request. (This could, for example, happen for a non-pipeline operation.) NOTE: the solutions for CVE-2023-28859 address data leakage across AsyncIO connections in general."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-459"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/redis/redis-py/pull/2641",
"refsource": "MISC",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/redis/redis-py/pull/2641"
},
{
"name": "https://github.com/redis/redis-py/issues/2665",
"refsource": "MISC",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/redis/redis-py/issues/2665"
},
{
"name": "https://github.com/redis/redis-py/releases/tag/v4.4.4",
"refsource": "MISC",
"tags": [
"Release Notes"
],
"url": "https://github.com/redis/redis-py/releases/tag/v4.4.4"
},
{
"name": "https://github.com/redis/redis-py/releases/tag/v4.5.4",
"refsource": "MISC",
"tags": [
"Release Notes"
],
"url": "https://github.com/redis/redis-py/releases/tag/v4.5.4"
},
{
"name": "https://github.com/redis/redis-py/pull/2666",
"refsource": "MISC",
"tags": [
"Release Notes"
],
"url": "https://github.com/redis/redis-py/pull/2666"
}
]
}
},
"impact": {
"baseMetricV3": {
"cvssV3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6
}
},
"lastModifiedDate": "2023-05-17T17:08Z",
"publishedDate": "2023-03-26T19: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.