1 個回答
- 最新
- 最多得票
- 最多評論
0
So after further research, I am 95% sure that despite vulnerability scans showing that the instances are simply running nginx 1.20.0, they are in fact running release 2.amzn2.0.4 of nginx 1.20.0. The vulnerability was patched in release 2.amzn2.0.3. The problem remains getting the security scan to accept this. One solution found is detailed here - https://github.com/aws/elastic-beanstalk-roadmap/issues/194 - essentially force an install of nginx 1.20.1 (or 1.20.2).
已回答 2 年前
相關內容
- 已提問 6 個月前
- 已提問 1 年前
AWS 官方已更新 2 年前- AWS 官方已更新 9 個月前
This answer matches the info found here: https://github.com/aws/elastic-beanstalk-roadmap/issues/221 . This is potentially very confusing. We've wasted days on this particular issue to satisfy a pen test audit (it's not clear how to update or change the nginx packages being used in the beanstalk images).
We also have a number of issues being flagged to CVE's related to openssh. This too appears to be an Amazon Specific build of openssh so it's currently unclear if these issues have been fixed and the pen test software is simply reporting a potential issue based on incorrectly understanding the package version that is running.