0.0
NA
CVE-2023-52630
Apache Struts SSRF
Description

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

INFO

Published Date :

April 2, 2024, 7:15 a.m.

Last Modified :

April 30, 2024, 9:15 a.m.

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67

Remotely Exploitable :

No

Impact Score :

Exploitability Score :

Affected Products

The following products are affected by CVE-2023-52630 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2023-52630 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2023-52630 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Apr. 30, 2024

    Action Type Old Value New Value
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Apr. 30, 2024

    Action Type Old Value New Value
    Changed Description In the Linux kernel, the following vulnerability has been resolved: blk-iocost: Fix an UBSAN shift-out-of-bounds warning When iocg_kick_delay() is called from a CPU different than the one which set the delay, @now may be in the past of @iocg->delay_at leading to the following warning: UBSAN: shift-out-of-bounds in block/blk-iocost.c:1359:23 shift exponent 18446744073709 is too large for 64-bit type 'u64' (aka 'unsigned long long') ... Call Trace: <TASK> dump_stack_lvl+0x79/0xc0 __ubsan_handle_shift_out_of_bounds+0x2ab/0x300 iocg_kick_delay+0x222/0x230 ioc_rqos_merge+0x1d7/0x2c0 __rq_qos_merge+0x2c/0x80 bio_attempt_back_merge+0x83/0x190 blk_attempt_plug_merge+0x101/0x150 blk_mq_submit_bio+0x2b1/0x720 submit_bio_noacct_nocheck+0x320/0x3e0 __swap_writepage+0x2ab/0x9d0 The underflow itself doesn't really affect the behavior in any meaningful way; however, the past timestamp may exaggerate the delay amount calculated later in the code, which shouldn't be a material problem given the nature of the delay mechanism. If @now is in the past, this CPU is racing another CPU which recently set up the delay and there's nothing this CPU can contribute w.r.t. the delay. Let's bail early from iocg_kick_delay() in such cases. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
    Removed Reference kernel.org https://git.kernel.org/stable/c/9f56f38331171c9a19754004f0664686d67ee48d
    Removed Reference kernel.org https://git.kernel.org/stable/c/1e4d3f8bd880e02932a9ea179f90bfa74fd2e899
    Removed Reference kernel.org https://git.kernel.org/stable/c/e5dc63f01e027721c29f82069f7e97e2149fa131
    Removed Reference kernel.org https://git.kernel.org/stable/c/27b216130e64651e76ed583742a1b4e4d08a67c3
    Removed Reference kernel.org https://git.kernel.org/stable/c/cd33b330cb21675189e747953845f5c3689e4912
    Removed Reference kernel.org https://git.kernel.org/stable/c/2a427b49d02995ea4a6ff93a1432c40fa4d36821
  • CVE Translated by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Apr. 30, 2024

    Action Type Old Value New Value
    Removed Translation Title: kernel de Linux Description: En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: blk-iocost: corrige una advertencia de desplazamiento fuera de los límites de UBSAN Cuando se llama a iocg_kick_delay() desde una CPU diferente a la que estableció el retraso, @now puede estar en el pasado de @iocg-&gt;delay_at genera la siguiente advertencia: UBSAN: shift-out-of-bounds in block/blk-iocost.c:1359:23 el exponente de desplazamiento 18446744073709 es demasiado grande para el tipo 'u64' de 64 bits ( también conocido como 'unsigned long long') ... Seguimiento de llamadas: dump_stack_lvl+0x79/0xc0 __ubsan_handle_shift_out_of_bounds+0x2ab/0x300 iocg_kick_delay+0x222/0x230 ioc_rqos_merge+0x1d7/0x2c0 __rq_qos_merge+0x2c/0x80 bio _intento_back_merge+0x83/0x190 blk_attempt_plug_merge+0x101/ 0x150 blk_mq_submit_bio+0x2b1/0x720 submit_bio_noacct_nocheck+0x320/0x3e0 __swap_writepage+0x2ab/0x9d0 El subdesbordamiento en sí no afecta realmente el comportamiento de ninguna manera significativa; sin embargo, la marca de tiempo anterior puede exagerar la cantidad de retraso calculada más adelante en el código, lo que no debería ser un problema material dada la naturaleza del mecanismo de retraso. Si @now está en el pasado, esta CPU está compitiendo con otra CPU que recientemente configuró el retraso y no hay nada que esta CPU pueda contribuir con el retraso. Salgamos temprano de iocg_kick_delay() en tales casos.
  • CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Apr. 02, 2024

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: blk-iocost: Fix an UBSAN shift-out-of-bounds warning When iocg_kick_delay() is called from a CPU different than the one which set the delay, @now may be in the past of @iocg->delay_at leading to the following warning: UBSAN: shift-out-of-bounds in block/blk-iocost.c:1359:23 shift exponent 18446744073709 is too large for 64-bit type 'u64' (aka 'unsigned long long') ... Call Trace: <TASK> dump_stack_lvl+0x79/0xc0 __ubsan_handle_shift_out_of_bounds+0x2ab/0x300 iocg_kick_delay+0x222/0x230 ioc_rqos_merge+0x1d7/0x2c0 __rq_qos_merge+0x2c/0x80 bio_attempt_back_merge+0x83/0x190 blk_attempt_plug_merge+0x101/0x150 blk_mq_submit_bio+0x2b1/0x720 submit_bio_noacct_nocheck+0x320/0x3e0 __swap_writepage+0x2ab/0x9d0 The underflow itself doesn't really affect the behavior in any meaningful way; however, the past timestamp may exaggerate the delay amount calculated later in the code, which shouldn't be a material problem given the nature of the delay mechanism. If @now is in the past, this CPU is racing another CPU which recently set up the delay and there's nothing this CPU can contribute w.r.t. the delay. Let's bail early from iocg_kick_delay() in such cases.
    Added Reference kernel.org https://git.kernel.org/stable/c/9f56f38331171c9a19754004f0664686d67ee48d [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/1e4d3f8bd880e02932a9ea179f90bfa74fd2e899 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/e5dc63f01e027721c29f82069f7e97e2149fa131 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/27b216130e64651e76ed583742a1b4e4d08a67c3 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/cd33b330cb21675189e747953845f5c3689e4912 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/2a427b49d02995ea4a6ff93a1432c40fa4d36821 [No types assigned]
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2023-52630 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2023-52630 weaknesses.

NONE - Vulnerability Scoring System
: