apache/incubator-seata

使用最新镜像【seataio/seata-server:latest】被检测出大量安全漏洞，要怎么处理呢？

Open

#5,528 opened on Apr 23, 2023

View on GitHub
 (29 comments) (0 reactions) (0 assignees)Java (25,960 stars) (8,878 forks)batch import
Securitygood first issuetask: help-wanted

Description

  • I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

使用Docker Hub上的seataio/seata-server:latest镜像被检测出大量安全漏洞 https://hub.docker.com/r/seataio/seata-server/tags

Ⅱ. Describe what happened

seataio/seata-server:latest镜像存在292个漏洞 image

If there is an exception, please attach the exception trace:

Just paste your stack trace here!

Ⅲ. Describe what you expected to happen

通过镜像部署seata后，上线安全测试检测出292个安全漏洞，涉及组件依赖，我们也不敢升级里面的组件

Ⅳ. How to reproduce it (as minimally and precisely as possible)

  1. 下载镜像
  2. 使用trivy进行安全检测

Minimal yet complete reproducer code (or URL to code):

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

  • JDK version(e.g. java -version):
  • Seata client/server version:
  • Database version:
  • OS(e.g. uname -a):
  • Others:

Contributor guide

Tech stack
javadocker
Domain
backendsecurity
Issue type
security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
DockerJavaSecurity vulnerability scanningSeata Dockerfile structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
First, replicate the vulnerability scan using Trivy on the seataio/seata server:latest image. Then, examine the Dockerfile in the repository (likely under server/docker/Dockerfile) to identify the base image and installed packages. Update vulnerable dependencies or switch to a more secure base image. Check the issue comments for any suggested fixes. Finally, submit a PR with the updated Dockerfile and verify the fix by rescanning.