Описание
When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path: 1. resolves symlink to its target and stores the resolved path for determining when output is written, 2. opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will: read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in step 1. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process. This issue was fixed in version 4.10.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | pending | 4.9-2ubuntu1 |
| esm-infra-legacy/trusty | not-affected | see notes |
| esm-infra-legacy/xenial | not-affected | see notes |
| esm-infra/bionic | released | 4.4-2ubuntu0.1~esm1 |
| esm-infra/focal | released | 4.7-1ubuntu0.1~esm1 |
| esm-infra/xenial | ignored | end of ESM support, was needs-triage |
| jammy | released | 4.8-1ubuntu2.1 |
| noble | released | 4.9-2ubuntu0.24.04.1 |
| questing | released | 4.9-2ubuntu0.25.10.1 |
| resolute | released | 4.9-2ubuntu1 |
Показывать по
EPSS
Связанные уязвимости
When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path: 1. resolves symlink to its target and stores the resolved path for determining when output is written, 2. opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will: read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in step 1. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process. This issue was fixed in version 4.10.
When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path: 1. resolves symlink to its target and stores the resolved path for determining when output is written, 2. opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will: read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in step 1. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process. This issue was fixed in version 4.10.
When sed is invoked with both -i (in-place edit) and --follow-symlinks ...
EPSS