elastic/logstash

S3 input output plugin might leak passwords

Open

#12,540 创建于 2020年12月30日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)Ruby (14,197 star) (3,496 fork)batch import
good first issue

描述

When you use minio or another S3 provider that uses path_style for buckets and do not configure this with the force_path_style then logstash while fail with a stacktrace which contains the S3 secret key. This was tested with secret key and key identifier present in the config. Not tested with a config file yet. probably config file is better.

贡献者指南

技术栈
无
领域
backendsecurity
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Logstash basicsS3 configuration
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Investigate the S3 input and output plugins' error handling to identify where the secret key is included in stack traces. Look for any existing code that redacts sensitive information. Consider modifying the error logging to exclude the secret key when displaying configuration errors. Review comments in the issue for any additional context.