Itai Greenhut

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** A flaw was found in the way the dumpable flag setting was handled when certain SUID binaries executed its descendants. The prerequisite is a SUID binary that sets real UID equal to effective UID, and real GID equal to effective GID. The descendant will then have a dumpable value set to 1. As a result, if the descendant process crashes and `core pattern` is set to a relative value, its core dump is stored in the current directory with uid:gid permissions. An unprivileged local user with eligible root SUID binary could use this flaw to place core dumps into root-owned directories, potentially resulting in escalation of privileges. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** apport (affected versions not specified) **Description** The issue concerns the `get pid info()` function in the data/apport component, which fails to properly parse the `/proc/pid/status` file from the kernel. This parsing issue may lead to potential security problems. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** apport (affected versions not specified) **Description** The issue concerns the `get starttime()` function in `data/apport`, which does not properly parse the `/proc/pid/stat` file from the kernel. This affects the correct analysis of the file. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** apport (affected versions not specified) **Description** The issue is related to apport in data/apport, where it does not properly open a report file. This prevents hanging reads on a FIFO. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.