Release Another Distro To Publish Images or Remediate CVE's
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 549
- Forks
- 277
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 2
Description
Hello!
The base image thats being leveraged currently is redhat-RHEL8 and comes with numerous CVE's. We were wondering if it would be possible to use a different base image or if there was a lighter image available? Or is it possible to remediate these CVE's by bumping the os version?
Here are the CVE's:
| Repository | Tag | Distro | CVE ID | Severity | Packages | Source Package | Package Version | Package License | Fix Status | Description |
|---|---|---|---|---|---|---|---|---|---|---|
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-0286 | high | cryptography | 3.3.2 | BSD or Apache License, Version 2.0 | fixed in 39.0.1 | There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-23931 | medium | cryptography | 3.3.2 | BSD or Apache License, Version 2.0 | fixed in 39.0.1 | cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions Cipher.update_into would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as bytes) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since update_into was originally introduced in cryptography 1.8. |
|
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | PRISMA-2022-0168 | high | pip | 9.0.3 | MIT | open | An issue was discovered in pip (all versions) because it installs the version with the highest version number, even if the user had intended to obtain a private package from a private index. This only affects use of the --extra-index-url option, and exploitation requires that the package does not already exist in the public index (and thus the attacker can put the package there with an arbitrary version number). NOTE: it has been reported that this is intended functionality and the user is responsible for using --extra-index-url securely. This vulnerability was first assigned with CVE-2018-20225, but it is still under dispute. However, this vulnerability still poses a threat when using the --extra-index-url. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-24056 | moderate | pkgconf-pkg-config | 1.4.2-1.el8 | ISC | affected | In pkgconf through 1.9.3, variable duplication can cause unbounded string expansion due to incorrect checks in libpkgconf/tuple.c:pkgconf_tuple_parse. For example, a .pc file containing a few hundred bytes can expand to one billion bytes. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2022-3715 | moderate | bash | 4.4.20-4.el8_6 | GPLv3+ | affected | A flaw was found in the bash package, where a heap-buffer overflow can occur in valid parameter_transform. This issue may lead to memory problems. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2022-43552 | low | libcurl | 7.61.1-25.el8_7.2 | MIT | affected | A use after free vulnerability exists in curl <7.87.0. Curl can be asked to tunnel virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2022-43995 | important | sudo | 1.8.29-8.el8_7.1 | ISC | under investigation | Sudo 1.8.0 through 1.9.12, with the crypt() password backend, contains a plugins/sudoers/auth/passwd.c array-out-of-bounds error that can result in a heap-based buffer over-read. This can be triggered by arbitrary local users with access to Sudo by entering a password of seven characters or fewer. The impact could vary depending on the system libraries, compiler, and processor architecture. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2017-14501 | low | libarchive | 3.3.3-4.el8 | BSD | affected | An out-of-bounds read flaw exists in parse_file_info in archive_read_support_format_iso9660.c in libarchive 3.3.2 when extracting a specially crafted iso9660 iso file, related to archive_read_format_iso9660_read_header. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2022-4304 | moderate | openssl-libs | 1.1.1k-7.el8_6 | OpenSSL and ASL 2.0 | affected | A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-23916 | moderate | libcurl | 7.61.1-25.el8_7.2 | MIT | affected | An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2022-35252 | low | curl | 7.61.1-25.el8_7.2 | MIT | affected | When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2021-35937 | moderate | rpm | 4.14.3-24.el8_7 | GPLv2+ | affected | A race condition vulnerability was found in rpm. A local unprivileged user could use this flaw to bypass the checks that were introduced in response to CVE-2017-7500 and CVE-2017-7501, potentially gaining root privileges. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2021-44568 | low | libsolv | 0.7.20-4.el8_7 | BSD | affected | Two heap-overflow vulnerabilities exist in openSUSE/libsolv libsolv through 13 Dec 2020 in the decisionmap variable via the resolve_dependencies function at src/solver.c (line 1940 & line 1995), which could cause a remote Denial of Service. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2021-35938 | moderate | rpm | 4.14.3-24.el8_7 | GPLv2+ | affected | A symbolic link issue was found in rpm. It occurs when rpm sets the desired permissions and credentials after installing a file. A local unprivileged user could use this flaw to exchange the original file with a symbolic link to a security-critical file and escalate their privileges on the system. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-24329 | important | python3-libs | 3.6.8-48.el8_7.1 | Python | under investigation | An issue in the urllib.parse component of Python before v3.11 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2021-35938 | moderate | rpm-libs | 4.14.3-24.el8_7 | GPLv2+ and LGPLv2+ with exceptions | affected | A symbolic link issue was found in rpm. It occurs when rpm sets the desired permissions and credentials after installing a file. A local unprivileged user could use this flaw to exchange the original file with a symbolic link to a security-critical file and escalate their privileges on the system. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-0361 | moderate | gnutls | 3.6.16-5.el8_6 | GPLv3+ and LGPLv2+ | affected | A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-0054 | low | vim-minimal | 8.0.1763-19.el8_6.4 | Vim and MIT | affected | Out-of-bounds Write in GitHub repository vim/vim prior to 9.0.1145. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2021-35939 | moderate | rpm-libs | 4.14.3-24.el8_7 | GPLv2+ and LGPLv2+ with exceptions | affected | It was found that the fix for CVE-2017-7500 and CVE-2017-7501 was incomplete: the check was only implemented for the parent directory of the file to be created. A local unprivileged user who owns another ancestor directory could potentially use this flaw to gain root privileges. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2022-2206 | low | vim-minimal | 8.0.1763-19.el8_6.4 | Vim and MIT | affected | Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2022-4293 | low | vim-minimal | 8.0.1763-19.el8_6.4 | Vim and MIT | under investigation | Floating Point Comparison with Incorrect Operator in GitHub repository vim/vim prior to 9.0.0804. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2022-4450 | moderate | openssl-libs | 1.1.1k-7.el8_6 | OpenSSL and ASL 2.0 | affected | The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as th | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-24056 | moderate | pkgconf | 1.4.2-1.el8 | ISC | affected | In pkgconf through 1.9.3, variable duplication can cause unbounded string expansion due to incorrect checks in libpkgconf/tuple.c:pkgconf_tuple_parse. For example, a .pc file containing a few hundred bytes can expand to one billion bytes. | |
| splunk/universalforwarder | 8.2.10 | redhat-RHEL8 | CVE-2023-24329 | important | platform-python | 3.6.8-48.el8_7.1 | Python | under investigation | An issue in the urllib.parse component of Python before v3.11 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters. |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Docker image build entry point for splunk/universalforwarder:8.2.10 and inspect how the RHEL8 base and listed packages are selected. Done means agreeing on a base-image or OS/package update that addresses the reported CVEs and producing a refreshed image scan; the issue names no file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, infrastructure, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100