CWE-61 vulnerabilities

A path traversal vulnerability exists in aiohttp versions prior to 3.8.5 when serving static routes with compressed file variants (.gz or .br) that are symbolic links. The server's default protection against path traversal does not apply to these compressed variants, allowing symbolic links to be followed outside the root directory. This can lead to unauthorized file access if such symbolic links point outside the intended directory or if users can create/upload them.

Dell Encryption Admin Utilities versions prior to 11.10.2 contain an Improper Link Resolution vulnerability. A local malicious user could potentially exploit this vulnerability, leading to privilege escalation.

After completing a build with AWS Serverless Application Model Command Line Interface (SAM CLI) which include symlinks, the content of those symlinks are copied to the cache of the local workspace as regular files or directories. As a result, a user who does not have access to those symlinks outside of the Docker container would now have access via the local workspace. Users should upgrade to version 1.134.0 and ensure any forked or derivative code is patched to incorporate the new fixes. After upgrading, users must re-build their applications using the sam build --use-container to update the symlinks.

When running the AWS Serverless Application Model Command Line Interface (SAM CLI) build process with Docker and symlinks are included in the build files, the container environment allows a user to access privileged files on the host by leveraging the elevated permissions granted to the tool. A user could leverage the elevated permissions to access restricted files via symlinks and copy them to a more permissive location on the container. Users should upgrade to v1.133.0 or newer and ensure any forked or derivative code is patched to incorporate the new fixes.

CVE-2024-45339 is a high-severity vulnerability in the golang/glog logging library where symbolic link (symlink) following can lead to unauthorized file overwrites. When logs are written to a widely-writable directory, an attacker can create a symlink pointing to a sensitive file. A privileged process writing logs may follow this symlink and overwrite the sensitive file. The vulnerability is addressed by causing the program to exit with status code 2 if the log file already exists, preventing overwriting via symlinks.

readline.sh in socat before1.8.0.2 relies on the /tmp/$USER/stderr2 file.