Update/harden docker.io/lmenezes/cerebro

[hannes-ucsc]

We currently use 0.9.4

built from this https://github.com/lmenezes/cerebro-docker/blob/master/Dockerfile

Fork that repo and modify the Dockerfile to harden the image. They are pushing to ghcr.io so their most recently built images are not on docker.io for some reason.

This process is similar to what we did for the pycharm image (fork, modify dockerfile, modify GH actions config, push to our org on docker.io).

• [ ] Security design review completed; the Resolution of this issue does not …
  • [x] … affect authentication; for example:
  • OAuth 2.0 with the application (API or Swagger UI)
  • Authentication of developers with Google Cloud APIs
  • Authentication of developers with AWS APIs
  • Authentication with a GitLab instance in the system
  • Password and 2FA authentication with GitHub
  • API access token authentication with GitHub
  • Authentication with
  • [x] … affect the permissions of internal users like access to
  • Cloud resources on AWS and GCP
  • GitLab repositories, projects and groups, administration
  • an EC2 instance via SSH
  • GitHub issues, pull requests, commits, commit statuses, wikis, repositories, organizations
  • [x] … affect the permissions of external users like access to
  • TDR snapshots
  • [x] … affect permissions of service or bot accounts
  • Cloud resources on AWS and GCP
  • [x] … affect audit logging in the system, like
  • adding, removing or changing a log message that represents an auditable event
  • changing the routing of log messages through the system
  • [x] … affect monitoring of the system
  • [ ] ~… introduce a new software dependency like~ https://github.com/DataBiosphere/azul/issues/5294#issuecomment-1581699076
  • Python packages on PYPI
  • Command-line utilities
  • Docker images
  • Terraform providers
  • [x] … add an interface that exposes sensitive or confidential data at the security boundary
  • [x] … affect the encryption of data at rest
  • [x] … require persistence of sensitive or confidential data that might require encryption at rest
  • [x] … require unencrypted transmission of data within the security boundary
  • [x] … affect the network security layer; for example by
  • modifying, adding or removing firewall rules
  • modifying, adding or removing security groups
  • changing or adding a port a service, proxy or load balancer listens on
• [x] Documentation on any unchecked boxes is provided in comments below

[hannes-ucsc]

Security review: this change does introduce a newer version of a Docker images. That image will have significantly fewer vulnerabilities.

[hannes-ucsc]

We won't have time for this. It's importance is lower, now that we decided that vulnerabilities in images used exclusively outside if the security boundary aren't subject to the FedRAMP mitigation timeline.