GSD-2022-23634
Vulnerability from gsd - Updated: 2022-02-11 00:00Details
### Impact
Prior to `puma` version `5.6.2`, `puma` may not always call
`close` on the response body. Rails, prior to version `7.0.2.2`, depended on the
response body being closed in order for its `CurrentAttributes` implementation to
work correctly.
From Rails:
> Under certain circumstances response bodies will not be closed, for example
> a bug in a webserver[1] or a bug in a Rack middleware. In the event a
> response is not notified of a close, ActionDispatch::Executor will not know
> to reset thread local state for the next request. This can lead to data
> being leaked to subsequent requests, especially when interacting with
> ActiveSupport::CurrentAttributes.
The combination of these two behaviors (Puma not closing the body + Rails'
Executor implementation) causes information leakage.
### Patches
This problem is fixed in Puma versions 5.6.2 and 4.3.11.
This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
See: https://github.com/advisories/GHSA-wh98-p28r-vrc9
for details about the rails vulnerability
Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.
### Workarounds
Upgrade to Rails versions 7.0.2.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
The [Rails CVE](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1)
includes a middleware that can be used instead.
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2022-23634",
"description": "Puma is a Ruby/Rack web server built for parallelism. Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails\u0027 Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.",
"id": "GSD-2022-23634",
"references": [
"https://www.suse.com/security/cve/CVE-2022-23634.html",
"https://security.archlinux.org/CVE-2022-23634",
"https://www.debian.org/security/2022/dsa-5146",
"https://access.redhat.com/errata/RHSA-2022:5498"
]
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"affected": [
{
"package": {
"ecosystem": "RubyGems",
"name": "puma",
"purl": "pkg:gem/puma"
}
}
],
"aliases": [
"CVE-2022-23634",
"GHSA-rmj8-8hhh-gv5h"
],
"details": "### Impact\n\nPrior to `puma` version `5.6.2`, `puma` may not always call\n`close` on the response body. Rails, prior to version `7.0.2.2`, depended on the\nresponse body being closed in order for its `CurrentAttributes` implementation to\nwork correctly.\n\nFrom Rails:\n\n\u003e Under certain circumstances response bodies will not be closed, for example\n\u003e a bug in a webserver[1] or a bug in a Rack middleware. In the event a\n\u003e response is not notified of a close, ActionDispatch::Executor will not know\n\u003e to reset thread local state for the next request. This can lead to data\n\u003e being leaked to subsequent requests, especially when interacting with\n\u003e ActiveSupport::CurrentAttributes.\n\nThe combination of these two behaviors (Puma not closing the body + Rails\u0027\nExecutor implementation) causes information leakage.\n\n### Patches\n\nThis problem is fixed in Puma versions 5.6.2 and 4.3.11.\n\nThis problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.\n\nSee: https://github.com/advisories/GHSA-wh98-p28r-vrc9\nfor details about the rails vulnerability\n\nUpgrading to a patched Rails _or_ Puma version fixes the vulnerability.\n\n### Workarounds\n\nUpgrade to Rails versions 7.0.2.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.\n\nThe [Rails CVE](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email\u0026utm_source=footer\u0026pli=1)\nincludes a middleware that can be used instead.\n",
"id": "GSD-2022-23634",
"modified": "2022-02-11T00:00:00.000Z",
"published": "2022-02-11T00:00:00.000Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h"
},
{
"type": "WEB",
"url": "https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb"
}
],
"related": [
"CVE-2022-23633",
"GHSA-wh98-p28r-vrc9"
],
"schema_version": "1.4.0",
"severity": [
{
"score": 8.0,
"type": "CVSS_V3"
}
],
"summary": "Information Exposure with Puma when used with Rails"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "security-advisories@github.com",
"ID": "CVE-2022-23634",
"STATE": "PUBLIC",
"TITLE": "Information Exposure when using Puma with Rails"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "puma",
"version": {
"version_data": [
{
"version_value": "\u003e= 5.0.0, \u003c 5.6.2"
},
{
"version_value": "\u003c 4.3.11"
}
]
}
}
]
},
"vendor_name": "puma"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "Puma is a Ruby/Rack web server built for parallelism. Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails\u0027 Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails _or_ Puma version fixes the vulnerability."
}
]
},
"impact": {
"cvss": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8.0,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N",
"version": "3.1"
}
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h",
"refsource": "CONFIRM",
"url": "https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h"
},
{
"name": "https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb",
"refsource": "MISC",
"url": "https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb"
},
{
"name": "https://github.com/advisories/GHSA-rmj8-8hhh-gv5h",
"refsource": "MISC",
"url": "https://github.com/advisories/GHSA-rmj8-8hhh-gv5h"
},
{
"name": "https://github.com/advisories/GHSA-wh98-p28r-vrc9",
"refsource": "MISC",
"url": "https://github.com/advisories/GHSA-wh98-p28r-vrc9"
},
{
"name": "https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email\u0026utm_source=footer\u0026pli=1",
"refsource": "MISC",
"url": "https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email\u0026utm_source=footer\u0026pli=1"
},
{
"name": "DSA-5146",
"refsource": "DEBIAN",
"url": "https://www.debian.org/security/2022/dsa-5146"
},
{
"name": "[debian-lts-announce] 20220525 [SECURITY] [DLA 3023-1] puma security update",
"refsource": "MLIST",
"url": "https://lists.debian.org/debian-lts-announce/2022/05/msg00034.html"
},
{
"name": "GLSA-202208-28",
"refsource": "GENTOO",
"url": "https://security.gentoo.org/glsa/202208-28"
},
{
"name": "[debian-lts-announce] 20220827 [SECURITY] [DLA 3083-1] puma security update",
"refsource": "MLIST",
"url": "https://lists.debian.org/debian-lts-announce/2022/08/msg00015.html"
},
{
"name": "FEDORA-2022-de968d1b6c",
"refsource": "FEDORA",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TUBFJ44NCKJ34LECZRAP4N5VL6USJSIB/"
},
{
"name": "FEDORA-2022-52d0032596",
"refsource": "FEDORA",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L7NESIBFCNSR3XH7LXDPKVMSUBNUB43G/"
},
{
"name": "FEDORA-2022-7c8b29195f",
"refsource": "FEDORA",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F6YWGIIKL7KKTS3ZOAYMYPC7D6WQ5OA5/"
}
]
},
"source": {
"advisory": "GHSA-rmj8-8hhh-gv5h",
"discovery": "UNKNOWN"
}
},
"github.com/rubysec/ruby-advisory-db": {
"cve": "2022-23634",
"cvss_v3": 8.0,
"date": "2022-02-11",
"description": "### Impact\n\nPrior to `puma` version `5.6.2`, `puma` may not always call\n`close` on the response body. Rails, prior to version `7.0.2.2`, depended on the\nresponse body being closed in order for its `CurrentAttributes` implementation to\nwork correctly.\n\nFrom Rails:\n\n\u003e Under certain circumstances response bodies will not be closed, for example\n\u003e a bug in a webserver[1] or a bug in a Rack middleware. In the event a\n\u003e response is not notified of a close, ActionDispatch::Executor will not know\n\u003e to reset thread local state for the next request. This can lead to data\n\u003e being leaked to subsequent requests, especially when interacting with\n\u003e ActiveSupport::CurrentAttributes.\n\nThe combination of these two behaviors (Puma not closing the body + Rails\u0027\nExecutor implementation) causes information leakage.\n\n### Patches\n\nThis problem is fixed in Puma versions 5.6.2 and 4.3.11.\n\nThis problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.\n\nSee: https://github.com/advisories/GHSA-wh98-p28r-vrc9\nfor details about the rails vulnerability\n\nUpgrading to a patched Rails _or_ Puma version fixes the vulnerability.\n\n### Workarounds\n\nUpgrade to Rails versions 7.0.2.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.\n\nThe [Rails CVE](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email\u0026utm_source=footer\u0026pli=1)\nincludes a middleware that can be used instead.\n",
"gem": "puma",
"ghsa": "rmj8-8hhh-gv5h",
"patched_versions": [
"~\u003e 4.3.11",
"\u003e= 5.6.2"
],
"related": {
"cve": [
"2022-23633"
],
"ghsa": [
"wh98-p28r-vrc9"
],
"url": [
"https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb"
]
},
"title": "Information Exposure with Puma when used with Rails",
"url": "https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h"
},
"gitlab.com": {
"advisories": [
{
"affected_range": "\u003c4.3.11||\u003e=5.0.0 \u003c5.6.2",
"affected_versions": "All versions before 4.3.11, all versions starting from 5.0.0 before 5.6.2",
"cvss_v2": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
"cvss_v3": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"cwe_ids": [
"CWE-1035",
"CWE-404",
"CWE-937"
],
"date": "2023-07-13",
"description": "Puma is a Ruby/Rack web server built for parallelism. Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails\u0027 Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.",
"fixed_versions": [],
"identifier": "CVE-2022-23634",
"identifiers": [
"CVE-2022-23634",
"GHSA-rmj8-8hhh-gv5h",
"GHSA-wh98-p28r-vrc9"
],
"not_impacted": "",
"package_slug": "gem/gitlab-puma",
"pubdate": "2022-02-11",
"solution": "Unfortunately, there is no solution available yet.",
"title": "Information Exposure when using Puma with Rails",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2022-23634",
"https://github.com/advisories/GHSA-rmj8-8hhh-gv5h",
"https://github.com/advisories/GHSA-wh98-p28r-vrc9",
"https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb",
"https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ"
],
"uuid": "5d6e201c-6e97-42e7-9fe7-dae7e03478db"
},
{
"affected_range": "\u003c4.3.11||\u003e=5.0.0 \u003c5.6.2",
"affected_versions": "All versions before 4.3.11, all versions starting from 5.0.0 before 5.6.2",
"cvss_v2": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
"cvss_v3": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"cwe_ids": [
"CWE-1035",
"CWE-404",
"CWE-937"
],
"date": "2023-07-13",
"description": "Puma is a Ruby/Rack web server built for parallelism. Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails\u0027 Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.",
"fixed_versions": [
"4.3.11",
"5.6.2"
],
"identifier": "CVE-2022-23634",
"identifiers": [
"CVE-2022-23634",
"GHSA-rmj8-8hhh-gv5h",
"GHSA-wh98-p28r-vrc9"
],
"not_impacted": "All versions starting from 4.3.11 before 5.0.0, all versions starting from 5.6.2",
"package_slug": "gem/puma",
"pubdate": "2022-02-11",
"solution": "Upgrade to versions 4.3.11, 5.6.2 or above.",
"title": "Information Exposure when using Puma with Rails",
"urls": [
"https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h",
"https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb",
"https://github.com/advisories/GHSA-rmj8-8hhh-gv5h",
"https://github.com/advisories/GHSA-wh98-p28r-vrc9"
],
"uuid": "08779c8c-d71f-4221-aa91-aaa1e98674be"
}
]
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:puma:puma:*:*:*:*:*:ruby:*:*",
"cpe_name": [],
"versionEndExcluding": "5.6.2",
"versionStartIncluding": "5.0.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:puma:puma:*:*:*:*:*:ruby:*:*",
"cpe_name": [],
"versionEndExcluding": "4.3.11",
"vulnerable": true
}
],
"operator": "OR"
},
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:rubyonrails:rails:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "7.0.2.2",
"versionStartIncluding": "7.0.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:rubyonrails:rails:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "6.1.4.6",
"versionStartIncluding": "6.1.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:rubyonrails:rails:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "6.0.4.6",
"versionStartIncluding": "6.0.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:rubyonrails:rails:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "5.2.6.2",
"versionStartIncluding": "5.0.0",
"vulnerable": true
}
],
"operator": "OR"
},
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
}
],
"operator": "OR"
},
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "security-advisories@github.com",
"ID": "CVE-2022-23634"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "en",
"value": "Puma is a Ruby/Rack web server built for parallelism. Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails\u0027 Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails _or_ Puma version fixes the vulnerability."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-404"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h",
"refsource": "CONFIRM",
"tags": [
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h"
},
{
"name": "https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb",
"refsource": "MISC",
"tags": [
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb"
},
{
"name": "https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email\u0026utm_source=footer\u0026pli=1",
"refsource": "MISC",
"tags": [
"Mailing List",
"Mitigation",
"Patch",
"Third Party Advisory"
],
"url": "https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email\u0026utm_source=footer\u0026pli=1"
},
{
"name": "https://github.com/advisories/GHSA-rmj8-8hhh-gv5h",
"refsource": "MISC",
"tags": [
"Third Party Advisory"
],
"url": "https://github.com/advisories/GHSA-rmj8-8hhh-gv5h"
},
{
"name": "https://github.com/advisories/GHSA-wh98-p28r-vrc9",
"refsource": "MISC",
"tags": [
"Mitigation",
"Not Applicable",
"Third Party Advisory"
],
"url": "https://github.com/advisories/GHSA-wh98-p28r-vrc9"
},
{
"name": "DSA-5146",
"refsource": "DEBIAN",
"tags": [
"Third Party Advisory"
],
"url": "https://www.debian.org/security/2022/dsa-5146"
},
{
"name": "[debian-lts-announce] 20220525 [SECURITY] [DLA 3023-1] puma security update",
"refsource": "MLIST",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2022/05/msg00034.html"
},
{
"name": "GLSA-202208-28",
"refsource": "GENTOO",
"tags": [
"Third Party Advisory"
],
"url": "https://security.gentoo.org/glsa/202208-28"
},
{
"name": "[debian-lts-announce] 20220827 [SECURITY] [DLA 3083-1] puma security update",
"refsource": "MLIST",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2022/08/msg00015.html"
},
{
"name": "FEDORA-2022-de968d1b6c",
"refsource": "FEDORA",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TUBFJ44NCKJ34LECZRAP4N5VL6USJSIB/"
},
{
"name": "FEDORA-2022-52d0032596",
"refsource": "FEDORA",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L7NESIBFCNSR3XH7LXDPKVMSUBNUB43G/"
},
{
"name": "FEDORA-2022-7c8b29195f",
"refsource": "FEDORA",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F6YWGIIKL7KKTS3ZOAYMYPC7D6WQ5OA5/"
}
]
}
},
"impact": {
"baseMetricV2": {
"acInsufInfo": false,
"cvssV2": {
"accessComplexity": "MEDIUM",
"accessVector": "NETWORK",
"authentication": "NONE",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"confidentialityImpact": "PARTIAL",
"integrityImpact": "NONE",
"vectorString": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
"version": "2.0"
},
"exploitabilityScore": 8.6,
"impactScore": 2.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"severity": "MEDIUM",
"userInteractionRequired": false
},
"baseMetricV3": {
"cvssV3": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 3.6
}
},
"lastModifiedDate": "2023-07-13T16:31Z",
"publishedDate": "2022-02-11T22:15Z"
}
}
}
Loading…
Loading…
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.
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.
Loading…