dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-28955

MEDIUM · 5.9 CVSS v3.1 Published 2024-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Affected devices create coredump files when crashed, storing them with world-readable permission. Any local user of the device can examine the coredump files, and research the memory contents. As for the details of affected product names, model numbers, and versions, refer to the information provided by the respective vendors listed under [References].

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Affected devices create coredump files with world-readable permissions (e.g., 0666) when processes crash. Any local user can read these memory dumps, potentially exposing sensitive data such as credentials, keys, session tokens, and other in-memory secrets.

MitigationConfigure coredump generation to use restrictive file permissions (e.g., 0600) or disable coredumps if not required, and ensure coredump files are stored in protected directories with limited access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify if coredump generation is enabled
    Check the system resource limits using 'ulimit -c' or review /proc/sys/kernel/core_pattern and /proc/sys/kernel/core_uses_pid. Also check systemd-coredump if installed using 'coredumpctl list' or 'systemctl status systemd-coredump@*'.
    Affected if Coredump generation is enabled and processes can produce crash dumps
  2. Inspect coredump file permission settings
    Check the coredump configuration in /etc/security/limits.conf or /etc/security/limits.d/ for any 'core' soft/hard limits. For systemd systems, examine /etc/systemd/coredump.conf (or /etc/systemd/coredump.conf.d/*.conf) for the 'ProcessSizeMax' and 'Storage' settings. Also check the umask setting in shell profiles or system-wide login.defs.
    Affected if No restrictive umask (e.g., 0077) is set, or coredump permissions are explicitly set to 0666 or world-readable defaults
  3. Check coredump storage directory permissions
    Review the directory where coredumps are saved (typically /var/crash, /var/tmp, or the directory specified in core_pattern). List the directory contents with 'ls -la <coredump_directory>' and check group/other permissions on both the directory and any existing coredump files.
    Affected if The coredump storage directory or existing coredump files grant read access to all users (e.g., drwxrwxrwx or -rw-rw-rw-- permissions)
  4. Examine active coredump file permissions
    If any coredump files exist on the system (search in /var/crash, /var/tmp, application working directories, or the root filesystem with 'find / -name "core*" -type f 2>/dev/null'), inspect their permissions using 'ls -la' on each file.
    Affected if Any coredump file shows world-readable permissions (0666 or similar)
  5. Review system-wide security policies for coredumps
    Check if the kernel parameter kernel.core_pattern is set to pipe coredumps to a secure handler. Verify if /proc/sys/kernel/core_pattern contains '|' (pipe to program) which may indicate a custom handler, and review that handler's security configuration. Also check sysctl settings 'sysctl kernel.core_pattern' and 'sysctl -a | grep core'.
    Affected if Coredumps are being saved directly to the filesystem without restrictive permissions or secure handling

The environment is affected if coredumps are enabled and any coredump files or their storage directory grant world-readable (other) permissions, allowing any local user to read potentially sensitive memory contents.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure coredump generation to use restrictive file permissions (e.g., 0600) or disable coredumps if not required, and ensure coredump files are stored in protected directories with limited access.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28955 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data