0.0
NA
CVE-2024-26821
CVE-2023-0025: Apache Struts Command Execution Vulnerability
Description

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

INFO

Published Date :

April 17, 2024, 10:15 a.m.

Last Modified :

May 16, 2024, 1:15 p.m.

Source :

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

Remotely Exploitable :

No

Impact Score :

Exploitability Score :

Affected Products

The following products are affected by CVE-2024-26821 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-2024-26821 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2024-26821 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

    May. 16, 2024

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

    May. 16, 2024

    Action Type Old Value New Value
    Changed Description In the Linux kernel, the following vulnerability has been resolved: fs: relax mount_setattr() permission checks When we added mount_setattr() I added additional checks compared to the legacy do_reconfigure_mnt() and do_change_type() helpers used by regular mount(2). If that mount had a parent then verify that the caller and the mount namespace the mount is attached to match and if not make sure that it's an anonymous mount. The real rootfs falls into neither category. It is neither an anoymous mount because it is obviously attached to the initial mount namespace but it also obviously doesn't have a parent mount. So that means legacy mount(2) allows changing mount properties on the real rootfs but mount_setattr(2) blocks this. I never thought much about this but of course someone on this planet of earth changes properties on the real rootfs as can be seen in [1]. Since util-linux finally switched to the new mount api in 2.39 not so long ago it also relies on mount_setattr() and that surfaced this issue when Fedora 39 finally switched to it. Fix this. 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/95de4ad173ca0e61034f3145d66917970961c210
    Removed Reference kernel.org https://git.kernel.org/stable/c/31f71f2d7a081fc6c6bdf06865beedf6db5b0ca4
    Removed Reference kernel.org https://git.kernel.org/stable/c/2a7a31e1fb9717845d9d5e2a8c6e48848147801e
    Removed Reference kernel.org https://git.kernel.org/stable/c/46f5ab762d048dad224436978315cbc2fa79c630
  • CVE Translated by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 16, 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: fs: relajar las comprobaciones de permisos de mount_setattr() Cuando agregamos mount_setattr(), agregué comprobaciones adicionales en comparación con los ayudantes heredados do_reconfigure_mnt() y do_change_type() utilizados por el mount(2) normal. Si ese montaje tenía un padre, verifique que la persona que llama y el espacio de nombres del montaje coincidan y, de lo contrario, asegúrese de que sea un montaje anónimo. Los rootfs reales no entran en ninguna de las dos categorías. No es un montaje anónimo porque obviamente está adjunto al espacio de nombres de montaje inicial pero obviamente tampoco tiene un montaje principal. Eso significa que el montaje heredado (2) permite cambiar las propiedades de montaje en los rootfs reales, pero mount_setattr (2) bloquea esto. Nunca pensé mucho en esto pero, por supuesto, alguien en este planeta tierra cambia las propiedades de las raíces reales como se puede ver en [1]. Dado que util-linux finalmente cambió a la nueva API de montaje en 2.39 no hace mucho, también depende de mount_setattr() y surgió este problema cuando Fedora 39 finalmente cambió a ella. Arregla esto.
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 14, 2024

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

    Apr. 17, 2024

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: fs: relax mount_setattr() permission checks When we added mount_setattr() I added additional checks compared to the legacy do_reconfigure_mnt() and do_change_type() helpers used by regular mount(2). If that mount had a parent then verify that the caller and the mount namespace the mount is attached to match and if not make sure that it's an anonymous mount. The real rootfs falls into neither category. It is neither an anoymous mount because it is obviously attached to the initial mount namespace but it also obviously doesn't have a parent mount. So that means legacy mount(2) allows changing mount properties on the real rootfs but mount_setattr(2) blocks this. I never thought much about this but of course someone on this planet of earth changes properties on the real rootfs as can be seen in [1]. Since util-linux finally switched to the new mount api in 2.39 not so long ago it also relies on mount_setattr() and that surfaced this issue when Fedora 39 finally switched to it. Fix this.
    Added Reference kernel.org https://git.kernel.org/stable/c/95de4ad173ca0e61034f3145d66917970961c210 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/31f71f2d7a081fc6c6bdf06865beedf6db5b0ca4 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/2a7a31e1fb9717845d9d5e2a8c6e48848147801e [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/46f5ab762d048dad224436978315cbc2fa79c630 [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-2024-26821 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-2024-26821 weaknesses.

NONE - Vulnerability Scoring System
: