fkie_cve-2025-5054
Vulnerability from fkie_nvd
Published
2025-05-30 18:15
Modified
2025-06-02 17:32
Severity ?
4.7 (Medium) - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Summary
Race condition in Canonical apport up to and including 2.32.0 allows a local attacker to leak sensitive information via PID-reuse by leveraging namespaces. When handling a crash, the function `_check_global_pid_and_forward`, which detects if the crashing process resided in a container, was being called before `consistency_checks`, which attempts to detect if the crashing process had been replaced. Because of this, if a process crashed and was quickly replaced with a containerized one, apport could be made to forward the core dump to the container, potentially leaking sensitive information. `consistency_checks` is now being called before `_check_global_pid_and_forward`. Additionally, given that the PID-reuse race condition cannot be reliably detected from userspace alone, crashes are only forwarded to containers if the kernel provided a pidfd, or if the crashing process was unprivileged (i.e., if dump mode == 1).
References
security@ubuntu.comhttps://ubuntu.com/security/CVE-2025-5054
security@ubuntu.comhttps://ubuntu.com/security/notices/USN-7545-1
security@ubuntu.comhttps://www.qualys.com/2025/05/29/apport-coredump/apport-coredump.txt
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Race condition in Canonical apport up to and including 2.32.0 allows a local attacker to leak sensitive information via PID-reuse by leveraging namespaces.\n\n\n\n\nWhen handling a crash, the function `_check_global_pid_and_forward`, which detects if the crashing process resided in a container, was being called before `consistency_checks`, which attempts to detect if the crashing process had been replaced. Because of this, if a process crashed and was quickly replaced with a containerized one, apport could be made to forward the core dump to the container, potentially leaking sensitive information. `consistency_checks` is now being called before `_check_global_pid_and_forward`. Additionally, given that the PID-reuse race condition cannot be reliably detected from userspace alone, crashes are only forwarded to containers if the kernel provided a pidfd, or if the crashing process was unprivileged (i.e., if dump mode == 1)."
    },
    {
      "lang": "es",
      "value": "La condici\u00f3n de ejecuci\u00f3n en Canonical Apport (hasta la versi\u00f3n 2.32.0 incluida) permite a un atacante local filtrar informaci\u00f3n confidencial mediante la reutilizaci\u00f3n de PID aprovechando los espacios de nombres. Al gestionar un fallo, la funci\u00f3n `_check_global_pid_and_forward`, que detecta si el proceso causante del fallo reside en un contenedor, se invocaba antes que `consistency_checks`, que intenta detectar si el proceso causante del fallo ha sido reemplazado. Por ello, si un proceso falla y se reemplaza r\u00e1pidamente por uno contenedorizado, se pod\u00eda ejecutar `apport` para reenviar el volcado de memoria al contenedor, lo que podr\u00eda filtrar informaci\u00f3n confidencial. `consistency_checks` ahora se invoca antes que `_check_global_pid_and_forward`. Adem\u00e1s, dado que la condici\u00f3n de ejecuci\u00f3n de reutilizaci\u00f3n de PID no se puede detectar de forma fiable solo desde el espacio de usuario, los fallos solo se reenv\u00edan a los contenedores si el n\u00facleo proporcion\u00f3 un pidfd o si el proceso causante del fallo no ten\u00eda privilegios (es decir, si el modo de volcado es 1)."
    }
  ],
  "id": "CVE-2025-5054",
  "lastModified": "2025-06-02T17:32:17.397",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "LOCAL",
          "availabilityImpact": "NONE",
          "baseScore": 4.7,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.0,
        "impactScore": 3.6,
        "source": "security@ubuntu.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-05-30T18:15:32.670",
  "references": [
    {
      "source": "security@ubuntu.com",
      "url": "https://ubuntu.com/security/CVE-2025-5054"
    },
    {
      "source": "security@ubuntu.com",
      "url": "https://ubuntu.com/security/notices/USN-7545-1"
    },
    {
      "source": "security@ubuntu.com",
      "url": "https://www.qualys.com/2025/05/29/apport-coredump/apport-coredump.txt"
    }
  ],
  "sourceIdentifier": "security@ubuntu.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-362"
        }
      ],
      "source": "security@ubuntu.com",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.