Skip to content

Commit 4ee62c9

Browse files
committed
e2e: update one cve description change
1 parent 429c701 commit 4ee62c9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

e2etests/node_scan_rhcos_test.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ var vulnLibksba = &v1.Vulnerability{
3535
// vulnTar is an example of a non-fixable vulnerability (potentially one of many others that exist for this version)
3636
var vulnTar = &v1.Vulnerability{
3737
Name: "CVE-2005-2541",
38-
Description: "DOCUMENTATION: The MITRE CVE dictionary describes this issue as: Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges. \n STATEMENT: This CVE was assigned to what is the documented and expected behaviour of tar. There are currently no plans to change tar behaviour to strip setuid and setgid bits when extracting archives.",
38+
Description: "DOCUMENTATION: The MITRE CVE dictionary describes this issue as: Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges. \n STATEMENT: This CVE was assigned to what is the documented and expected behaviour of tar. There are currently no plans to change tar behaviour to strip setuid and setgid bits when extracting archives.\n\nThis vulnerability is considered moderate rather than important because the exploitation scenario requires specific conditions: the `tar` extraction must be performed by the root user, and the tarball itself must be crafted maliciously with setuid or setgid bits. In typical use cases, users do not routinely extract untrusted tar files as root, reducing the likelihood of exploitation. Additionally, non-root extractions do not preserve these bits unless explicitly requested with the `-p` option. Someone who is extracting untrusted tar files is equivalent to someone just taking a random Python script and running it.\n MITIGATION: To mitigate the risks associated with this vulnerability, avoid extracting tar files as the root user, especially when dealing with untrusted sources. Instead, perform extractions as a non-root user or in a restricted environment. Use a dedicated, empty directory for extracting archives to prevent accidental exposure of sensitive files. After extraction, review the file permissions to check for unexpected setuid or setgid bits before granting access. When extraction as root is necessary, use the --no-same-permissions option to prevent preserving the setuid and setgid bits.",
3939
Link: "https://access.redhat.com/security/cve/CVE-2005-2541",
4040
MetadataV2: &v1.Metadata{
4141
CvssV2: nil,

0 commit comments

Comments
 (0)