Description
CVE-2025-45582 found in deb/debian/[email protected]+dfsg-1.2+deb12u1
Important
Risk: 0.97 (Low)
CVSS: 4.1
Description
GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal.
Affected component
The vulnerability is in pkg:deb/debian/[email protected]+dfsg-1.2+deb12u1, detected by github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning, github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning:test.
Recommended fix
No fix is available.
Additional guidance for mitigating vulnerabilities
Visit our guides on devguard.org
See more details...
Path to component
%%{init: { 'theme':'base', 'themeVariables': {
'primaryColor': '#F3F3F3',
'primaryTextColor': '#0D1117',
'primaryBorderColor': '#999999',
'lineColor': '#999999',
'secondaryColor': '#ffffff',
'tertiaryColor': '#ffffff'
} }}%%
flowchart TD
root(["root"]) --- github_com_l3montree_dev_devguard_cmd_devguard_scanner_container_scanning(["github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning"])
github_com_l3montree_dev_devguard_cmd_devguard_scanner_container_scanning(["github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning"]) --- debian_12_7(["debian\@12.7"])
debian_12_7(["debian\@12.7"]) --- debian_dash(["debian/dash"])
debian_dash(["debian/dash"]) --- debian_dpkg(["debian/dpkg"])
debian_dpkg(["debian/dpkg"]) --- debian_tar(["debian/tar"])
debian_12_7(["debian\@12.7"]) --- debian_gnupg(["debian/gnupg"])
debian_gnupg(["debian/gnupg"]) --- debian_dirmngr(["debian/dirmngr"])
debian_dirmngr(["debian/dirmngr"]) --- debian_gpgconf(["debian/gpgconf"])
debian_gpgconf(["debian/gpgconf"]) --- debian_libreadline8(["debian/libreadline8"])
debian_libreadline8(["debian/libreadline8"]) --- debian_readline_common(["debian/readline-common"])
debian_readline_common(["debian/readline-common"]) --- debian_dpkg(["debian/dpkg"])
debian_gnupg(["debian/gnupg"]) --- debian_gnupg_utils(["debian/gnupg-utils"])
debian_gnupg_utils(["debian/gnupg-utils"]) --- debian_libreadline8(["debian/libreadline8"])
debian_gnupg(["debian/gnupg"]) --- debian_gpg_agent(["debian/gpg-agent"])
debian_gpg_agent(["debian/gpg-agent"]) --- debian_gpgconf(["debian/gpgconf"])
debian_gnupg(["debian/gnupg"]) --- debian_gpg_wks_client(["debian/gpg-wks-client"])
debian_gpg_wks_client(["debian/gpg-wks-client"]) --- debian_dirmngr(["debian/dirmngr"])
debian_gpg_wks_client(["debian/gpg-wks-client"]) --- debian_gpg_agent(["debian/gpg-agent"])
debian_gpg_wks_client(["debian/gpg-wks-client"]) --- debian_gpg(["debian/gpg"])
debian_gpg(["debian/gpg"]) --- debian_gpgconf(["debian/gpgconf"])
debian_gpg(["debian/gpg"]) --- debian_libreadline8(["debian/libreadline8"])
debian_gnupg(["debian/gnupg"]) --- debian_gpg_wks_server(["debian/gpg-wks-server"])
debian_gpg_wks_server(["debian/gpg-wks-server"]) --- debian_gpg_agent(["debian/gpg-agent"])
debian_gpg_wks_server(["debian/gpg-wks-server"]) --- debian_gpg(["debian/gpg"])
debian_gnupg(["debian/gnupg"]) --- debian_gpg(["debian/gpg"])
debian_gnupg(["debian/gnupg"]) --- debian_gpgsm(["debian/gpgsm"])
debian_gpgsm(["debian/gpgsm"]) --- debian_gpgconf(["debian/gpgconf"])
debian_gpgsm(["debian/gpgsm"]) --- debian_libreadline8(["debian/libreadline8"])
debian_12_7(["debian\@12.7"]) --- debian_grep(["debian/grep"])
debian_grep(["debian/grep"]) --- debian_dpkg(["debian/dpkg"])
debian_12_7(["debian\@12.7"]) --- debian_gzip(["debian/gzip"])
debian_gzip(["debian/gzip"]) --- debian_dpkg(["debian/dpkg"])
debian_12_7(["debian\@12.7"]) --- debian_mercurial(["debian/mercurial"])
debian_mercurial(["debian/mercurial"]) --- debian_python3(["debian/python3"])
debian_python3(["debian/python3"]) --- debian_libpython3_stdlib(["debian/libpython3-stdlib"])
debian_libpython3_stdlib(["debian/libpython3-stdlib"]) --- debian_libpython3_11_stdlib(["debian/libpython3.11-stdlib"])
debian_libpython3_11_stdlib(["debian/libpython3.11-stdlib"]) --- debian_libreadline8(["debian/libreadline8"])
debian_python3(["debian/python3"]) --- debian_python3_11(["debian/python3.11"])
debian_python3_11(["debian/python3.11"]) --- debian_libpython3_11_stdlib(["debian/libpython3.11-stdlib"])
debian_12_7(["debian\@12.7"]) --- debian_python3_minimal(["debian/python3-minimal"])
debian_python3_minimal(["debian/python3-minimal"]) --- debian_dpkg(["debian/dpkg"])
root(["root"]) --- github_com_l3montree_dev_devguard_cmd_devguard_scanner_container_scanning_test(["github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning:test"])
github_com_l3montree_dev_devguard_cmd_devguard_scanner_container_scanning_test(["github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning:test"]) --- debian_12_7(["debian\@12.7"])
classDef default stroke-width:2px
| Risk Factor | Value | Description |
|---|---|---|
| Vulnerability Depth | 2 |
The vulnerability is in a dependency of a dependency in your project. It is 2 levels deep. |
| EPSS | 0.00 % |
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days. |
| EXPLOIT | Not available |
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database. There are no script kiddies exploiting this vulnerability. |
| CVSS-BE | 4.2 |
|
| CVSS-B | 4.1 |
- The vulnerability requires local access to the device to be exploited. - It is difficult for an attacker to exploit this vulnerability and may require special conditions. - An attacker does not need any special privileges or access rights. - The attacker needs the user to perform some action, like clicking a link. - The vulnerability can affect other systems as well, not just the initial system. - There is a low impact on the integrity of the data. - There is a low impact on the availability of the system. |
More details can be found in DevGuard
Interact with this vulnerability
You can use the following slash commands to interact with this vulnerability:
👍 Reply with this to acknowledge and accept the identified risk.
/accept I accept the risk of this vulnerability, because ...
⚠️ Mark the risk as false positive: Use one of these commands if you believe the reported vulnerability is not actually a valid issue.
/component-not-present The vulnerable component is not included in the artifact.
/vulnerable-code-not-present The component is present, but the vulnerable code is not included or compiled.
/vulnerable-code-not-in-execute-path The vulnerable code exists, but is never executed at runtime.
/vulnerable-code-cannot-be-controlled-by-adversary Built-in protections prevent exploitation of this vulnerability.
/inline-mitigations-already-exist The vulnerable code cannot be controlled or influenced by an attacker.
🔁 Reopen the risk: Use this command to reopen a previously closed or accepted vulnerability.
/reopen ...