Skip to content

Elastic Open Crawler - Recent Container CVEs #430

@Skagnatti

Description

@Skagnatti

Hello,

I have been using the Elastic Open Crawler for some time now. In general, it has been a nice, functional replacement for the deprecated Enterprise Search Crawler.

When my Elastic Open Crawler container(s) launch, they launch with either the docker.elastic.co/integrations/crawler:latest or docker.elastic.co/integrations/crawler:0.4.2 image.

docker ps
CONTAINER ID   IMAGE                                           COMMAND       CREATED        STATUS        PORTS     NAMES
6c52ec83e23e   docker.elastic.co/integrations/crawler:latest   "/bin/bash"   20 hours ago   Up 20 hours             crawler
bash-5.3$ cat product_version
0.4.2

Within the running container the rack version appears to be different than the recently pushed CVE fixes:

bash-5.3$ egrep 'rack|java' Gemfile Gemfile.lock
Gemfile:  gem 'rack', '~> 2.2.14'

Gemfile.lock:    rack (2.2.16)
Gemfile.lock:      rack (>= 1.0.0)
Gemfile.lock:  universal-java-17
Gemfile.lock:  universal-java-21
Gemfile.lock:  universal-java-22
Gemfile.lock:  universal-java-23
Gemfile.lock:  rack (~> 2.2.14)

And I suppose for the other ruby-maven removal CVE in the Dockerfile.

Metadata

Metadata

Type

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions