critical

CVE-2017-7811

Memory safety bugs were reported in Firefox 55.

Published 11 Jun 2018Modified 17 Jun 2026CWE 119

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.8CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by NVD. Rated lower by Ubuntu (medium).

Description

Memory safety bugs were reported in Firefox 55. Some of these bugs showed evidence of memory corruption and we presume that with enough effort that some of these could be exploited to run arbitrary code. This vulnerability affects Firefox < 56.

Affected packages and fixed versions

Source	Package	Fixed in
ubuntu 14.04	firefox	56.0+build6-0ubuntu0.14.04.1
ubuntu 16.04	firefox	56.0+build6-0ubuntu0.16.04.1
ubuntu 17.04	firefox	56.0+build6-0ubuntu0.17.04.1
ubuntu 17.10	firefox	56.0+build6-0ubuntu1
ubuntu 18.04	firefox	56.0+build6-0ubuntu1
ubuntu 18.10	firefox	56.0+build6-0ubuntu1
ubuntu 19.04	firefox	56.0+build6-0ubuntu1
ubuntu 19.10	firefox	56.0+build6-0ubuntu1
ubuntu 20.04	firefox	56.0+build6-0ubuntu1
ubuntu 20.10	firefox	56.0+build6-0ubuntu1
ubuntu 21.04	firefox	56.0+build6-0ubuntu1
ubuntu 21.10	firefox	56.0+build6-0ubuntu1

Show all 17 entries from 17 sources

Source	Package	Fixed in
ubuntu 14.04	firefox	56.0+build6-0ubuntu0.14.04.1
ubuntu 16.04	firefox	56.0+build6-0ubuntu0.16.04.1
ubuntu 17.04	firefox	56.0+build6-0ubuntu0.17.04.1
ubuntu 17.10	firefox	56.0+build6-0ubuntu1
ubuntu 18.04	firefox	56.0+build6-0ubuntu1
ubuntu 18.10	firefox	56.0+build6-0ubuntu1
ubuntu 19.04	firefox	56.0+build6-0ubuntu1
ubuntu 19.10	firefox	56.0+build6-0ubuntu1
ubuntu 20.04	firefox	56.0+build6-0ubuntu1
ubuntu 20.10	firefox	56.0+build6-0ubuntu1
ubuntu 21.04	firefox	56.0+build6-0ubuntu1
ubuntu 21.10	firefox	56.0+build6-0ubuntu1
ubuntu 22.04	firefox	56.0+build6-0ubuntu1
ubuntu 22.10	firefox	56.0+build6-0ubuntu1
ubuntu 23.04	firefox	56.0+build6-0ubuntu1
ubuntu 23.10	firefox	56.0+build6-0ubuntu1
ubuntu 24.04	firefox	56.0+build6-0ubuntu1

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs