Researchers find hidden vulnerabilities in hundreds of Docker containers
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2019-17558 | Remote Code Execution via VelocityResponseWriter plug-in in Apache Solr 5.0–8.3.1 CVE-2019-17558 is a remote code execution flaw in the VelocityResponseWriter plug-in of Apache Solr 5.0.0 through 8.3.1, caused by improper handling of Velocity template content (CWE-74). An attacker can supply a renderable, potentially malicious Velocity template either from the configset's velocity/ directory or, when a response writer has been configured with params.resource.loader.enabled set to true (which requires Config API access), directly via request parameters; parameter-provided templates are disabled by default and the vulnerable path was removed entirely in Solr 8.4. Successful exploitation allows a remote attacker to execute arbitrary code with the privileges of the Solr process, risking compromise of the host and indexed data. Any Solr deployment running 5.0.0–8.3.1 is affected, and Oracle Primavera Unifier is also impacted because it bundles the affected Solr component. The flaw is under active exploitation: it was added to CISA's Known Exploited Vulnerabilities catalog on 2021-11-03, with EPSS estimating a 98.6% probability of exploitation in the next 30 days. Do: Upgrade to Apache Solr 8.4 or later per vendor instructions (CISA's required action). If upgrading is deferred, avoid enabling params.resource.loader.enabled on custom response writers, restrict access to the Solr Config API, limit Solr's network exposure, and review access logs for requests passing velocity template parameters. Oracle Primavera Unifier customers should apply the applicable Oracle Critical Patch Update. | 7.5 | 99% | KEV PoC ×4 |
| largetens of thousands of internet-exposed Solr instances (≈20,000–30,000 in public scans), with exploitation further limited to instances that enabled the params… | |
| CVE-2021-41773 | Path Traversal to RCE in Apache HTTP Server 2.4.49 Apache HTTP Server contains a path traversal flaw (CWE-22) that lets crafted HTTP requests reach files outside directories configured via Alias-like directives. When files outside those aliased directories are not protected by the default 'require all denied' policy, attackers can read arbitrary files outside the intended root, and if CGI scripts are enabled the traversal can be escalated to remote code execution under the web server account. Anyone running an affected Apache HTTP Server release with such a configuration is exposed; the initial 2.4.50 patch was incomplete, so the flaw's full remediation is tracked under CVE-2021-42013. Exploitation is confirmed in the wild: CISA added the vulnerability to the KEV catalog on 2021-11-03 with known ransomware use, and EPSS assigns a ~100% probability of exploitation within 30 days (100th percentile). Do: Upgrade to Apache HTTP Server 2.4.51 or later; do not stop at 2.4.50, since its fix was incomplete (see CVE-2021-42013). As an interim mitigation, ensure directories referenced by Alias-like directives are covered by 'require all denied' and disable or restrict CGI (mod_cgi/mod_cgid) on traversable paths. Review access logs for traversal patterns such as /icons/../ and unexpected CGI invocations, and hunt for webshells or ransomware staging given the known ransomware use. | 9.8 | 100% | KEV ransomware PoC ×6 |
| masson the order of 100,000+ internet-exposed Apache servers | |
| CVE-2021-42013 | Path Traversal and RCE in Apache HTTP Server (follow-up to CVE-2021-41773) Apache HTTP Server contains a path traversal flaw (CWE-22) that can lead to remote code execution; CVE-2021-42013 resolves an incomplete patch previously issued for CVE-2021-41773. The flaw is triggered when files outside directories mapped by Alias-like directives are not protected by the default 'require all denied' configuration, or when CGI scripts are enabled, allowing an attacker to traverse outside the intended directory roots. An attacker can read files outside the configured paths, and where CGI script execution is enabled, achieve remote code execution on the server. The affected product per CISA is Apache HTTP Server; the source data does not specify exact version ranges, so defenders should consult the vendor advisory for fixed releases. Exploitation is confirmed in the wild: the vulnerability was added to CISA KEV on 2021-11-03 with known ransomware use, EPSS estimates a 100% probability of exploitation within 30 days, and no public PoC is listed. Do: Apply the Apache HTTP Server update per vendor instructions immediately, since this is a CISA KEV item with known ransomware use and near-certain near-term exploitation. Until patched, ensure directories targeted by Alias-like directives are covered by 'require all denied' defaults and disable CGI script execution where it is not required. Review access logs for path traversal probes and confirm no replaced version retains the incomplete earlier patch. | 9.8 | 100% | KEV ransomware PoC ×6 |
| massorder of 100,000+ internet-exposed Apache HTTP Server instances at disclosure time |
Full article412 words · extracted from helpnetsecurity.com · click to collapse
Rezilion uncovered the presence of hundreds of Docker container images containing vulnerabilities that are not detected by most standard vulnerability scanners and SCA tools.

The research revealed numerous high-severity/critical vulnerabilities hidden in hundreds of popular container images, downloaded billions of times collectively. This includes high-profile vulnerabilities with publicly known exploits.
Some of the hidden vulnerabilities are known to be actively exploited in the wild and are part of the CISA known exploited vulnerabilities catalog, including CVE-2021-42013, CVE-2021-41773, CVE-2019-17558.
The research dives deeper into one of the root causes identified in the assessment – the inability to detect software components not managed by package managers.
The study explains how the inherent method of operation of standard vulnerability scanners and SCA tools relies on acquiring data from package managers to know what packages exist in the scanned environment, making them susceptible to missing vulnerable software packages in multiple common scenarios in which software is deployed in ways that circumvent these package managers. This research shows precisely how wide this gap is and its impact on organizations using third-party software.
According to the report, package managers circumventing deployment methods are common in Docker containers. The research team has identified over 100,000 container images that deploy code in a way that bypasses the package managers, including most of DockerHub’s official container images. These containers either already contain hidden vulnerabilities or are prone to have hidden vulnerabilities if a vulnerability in one of these components is identified.
The researchers identified four different scenarios in which software is deployed without interaction with package managers, such as the application itself, runtimes required for the operation of the application, dependencies as necessary for the application to work, and dependencies required for the deployment/build process of the application that are not deleted at the end of the container image build process and shows how hidden vulnerabilities can find their way to the container images.
“We hope this research will educate developers and security practitioners of the existence of this gap so that they will be able to take appropriate actions to minimize the risk as well as push vendors and open-source projects to add support for these types of scenarios,” said Yotam Perkal, Director, Vulnerability Research at Rezilion. “It’s important to note that as long as vulnerability scanners and SCA tools fail to accommodate for these situations, any container image that installs packages or executables in this manner may eventually contain ‘hidden’ vulnerabilities if any of these components become vulnerable.”
Text extracted automatically; images, tables and formatting may be missing. Original: https://www.helpnetsecurity.com/2023/02/23/hidden-vulnerabilities-docker-containers/