NVD / CVE Program· CNA mitre

CVE-2011-0777: Use-after-free vulnerability in Google Chrome before 9.0.597.84 allows remote attackers to cause a denial of service or possibly have…

HighCVSS 7.5 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 73.9% of all records.
No special conditions are required; it is repeatable.
Fixed version: chromium-browser (Debian:6.0) 6.0.472.63~r59945-5+squeeze2.

Low priority for now. Upgrade to chromium-browser (Debian:6.0) 6.0.472.63~r59945-5+squeeze2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Use-after-free vulnerability in Google Chrome before 9.0.597.84 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to image loading.

DSA-2166-1

Published: Feb 4, 2011
Updated: Jun 16, 2026
EPSS: 1.4% · 73th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.4%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
google	chrome	cpe:2.3:a:google:chrome

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

google chromebefore 9.0.597.84

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:6.0	chromium-browser	before 6.0.472.63~r59945-5+squeeze2	6.0.472.63~r59945-5+squeeze2

Same product

google: all records

Other highest-scoring records for the same primary product.

CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of…KEV
95Now
CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a…KEV
90Now
CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a…KEV
90Now

Published before and after this one in the same product

← EarlierCVE-2011-0474Jan 14, 2011 · Google Chrome before 8.0.552.237 and Chrome OS before 8.0.552.344 do not properly handle Cascading Style Sheets (CSS) token sequences in…
41Plan
← EarlierCVE-2011-0776Feb 4, 2011 · The sandbox implementation in Google Chrome before 9.0.597.84 on Mac OS X might allow remote attackers to obtain potentially sensitive…
20Monitor
Later →CVE-2011-0778Feb 4, 2011 · Google Chrome before 9.0.597.84 does not properly restrict drag and drop operations, which might allow remote attackers to bypass the Same…
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:chromium-browser	6.0.472.63~r59945-5+squeeze2 · Debian:6.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

No special conditions are required; it is repeatable.

If successful

Confidentiality: P · data can be read
Integrity: P · data or configuration can be modified
Availability: P · the service can be disrupted

Attack complexity: Low
Confidentiality impact: P
Integrity impact: P
Availability impact: P

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

AV:N/AC:L/Au:N/C:P/I:P/A:P

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:49 PM UTC

For records you follow, these changes also arrive as notifications. →

References

googlechromereleases.blogspot.com/2011/02/stable-channel-update.html

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records