From d7650e36ec724a6ffcf6822ac675661aba6e9a19 Mon Sep 17 00:00:00 2001 From: sullo Date: Thu, 30 Jun 2022 13:59:37 -0400 Subject: [PATCH] Enhance one and fix yaml in the other --- cves/2021/CVE-2021-41282.yaml | 12 +++++++++--- cves/2022/CVE-2022-24856.yaml | 5 +++-- 2 files changed, 12 insertions(+), 5 deletions(-) diff --git a/cves/2021/CVE-2021-41282.yaml b/cves/2021/CVE-2021-41282.yaml index 971c79f985..b02f0a63b1 100644 --- a/cves/2021/CVE-2021-41282.yaml +++ b/cves/2021/CVE-2021-41282.yaml @@ -1,13 +1,17 @@ id: CVE-2021-41282 info: - name: pfSense Arbitrary File Write to RCE + name: pfSense - Arbitrary File Write author: cckuailong severity: high - description: diag_routes.php in pfSense 2.5.2 allows sed data injection. Authenticated users are intended to be able to view data about the routes set in the firewall. The data is retrieved by executing the netstat utility, and then its output is parsed via the sed utility. Although the common protection mechanisms against command injection (i.e., the usage of the escapeshellarg function for the arguments) are used, it is still possible to inject sed-specific code and write an arbitrary file in an arbitrary location. + description: | + diag_routes.php in pfSense 2.5.2 allows sed data injection. Authenticated users are intended to be able to view data about the routes set in the firewall. The data is retrieved by executing the netstat utility, and then its output is parsed via the sed utility. Although the common protection mechanisms against command injection (e.g., the usage of the escapeshellarg function for the arguments) are used, it is still possible to inject sed-specific code and write an arbitrary file in an arbitrary location. + remediation: | + Upgrade to pfSense CE software version 2.6.0 or later, or pfSense Plus software version 22.01 or later. reference: - https://www.shielder.it/advisories/pfsense-remote-command-execution/ - https://www.rapid7.com/db/modules/exploit/unix/http/pfsense_diag_routes_webshell/ + - https://docs.netgate.com/downloads/pfSense-SA-22_02.webgui.asc - https://nvd.nist.gov/vuln/detail/CVE-2021-41282 classification: cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H @@ -52,4 +56,6 @@ requests: dsl: - "contains(body, 'c3959e8a43f1b39b0d1255961685a238')" - "status_code==200" - condition: and \ No newline at end of file + condition: and + +# Enhanced by cs 06/30/2022 diff --git a/cves/2022/CVE-2022-24856.yaml b/cves/2022/CVE-2022-24856.yaml index 91a8fde735..429f7dfb1b 100644 --- a/cves/2022/CVE-2022-24856.yaml +++ b/cves/2022/CVE-2022-24856.yaml @@ -5,8 +5,9 @@ info: author: pdteam severity: high description: | - FlyteConsole prior to version 0.52.0 is vulnerable to server-side request forgery when FlyteConsole is open to the general internet. An attacker can exploit any user of a vulnerable instance to access the internal metadata server or other unauthenticated URLs. Passing of headers to an unauthorized actor may occur. -remediation: FlyteConsole is the web user interface for the Flyte platform. The patch for this issue deletes the entire `cors_proxy`, as this is not required for console anymore. A patch is available in FlyteConsole version 0.52.0. Or, disable FlyteConsole availability on the internet as a workaround. + FlyteConsole is the web user interface for the Flyte platform. FlyteConsole prior to version 0.52.0 is vulnerable to server-side request forgery when FlyteConsole is open to the general internet. An attacker can exploit any user of a vulnerable instance to access the internal metadata server or other unauthenticated URLs. Passing of headers to an unauthorized actor may occur. + remediation: | + The patch for this issue deletes the entire cors_proxy, as this is no longer required for the console. A patch is available in FlyteConsole version 0.52.0, or as a work-around disable FlyteConsole. reference: - https://github.com/flyteorg/flyteconsole/security/advisories/GHSA-www6-hf2v-v9m9 - https://github.com/flyteorg/flyteconsole/pull/389