On Sun, 2018-02-04 at 12:28 -0800, Noah Meyerhans wrote:
> On Sun, Feb 04, 2018 at 02:55:52PM +1100, Michael Schams wrote:
> > However, the AWS scan tool rejects the AMI due to the following
> > issue:
> >
> > (quote) "Vulnerabilities detected - The following vulnerabilities
> > were detected
On Sun, Feb 04, 2018 at 02:55:52PM +1100, Michael Schams wrote:
> However, the AWS scan tool rejects the AMI due to the following issue:
>
> (quote) "Vulnerabilities detected - The following vulnerabilities were
> detected and must be addressed: CVE-2017-5754 [3]."
Unfortunately, only the AWS
On Sun, 2018-02-04 at 14:55 +1100, Michael Schams wrote:
[...]
> The AMI I submitted has all available Debian updates installed and
> reading the description of CVE-2017-5754, this is clearly the
> Meltdown attack.
After launching the AMI, the kernel seems to be up-to-date and correct:
# uname
Hi everyone,
I am trying to publish a new AMI at the AWS Marketplace [1]. My AMI is
based on the Debian Stretch ami-628ad918 [2], which includes kernel
updates for DSA 4078, addressing the Meltdown attack.
However, the AWS scan tool rejects the AMI due to the following issue:
(quote)