WebRTC: memory corruption flaw under attack

What is affected

WebRTC is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

WebRTC, an open-source project providing web browsers with real-time communication, contains a heap buffer overflow vulnerability that allows an attacker to perform shellcode execution. This vulnerability impacts web browsers using WebRTC including but not limited to Google Chrome.

What an attacker can do

This is a memory corruption flaw. It lets an attacker corrupt the program's memory by feeding it specially crafted content: a web page, a file or a network message. The result ranges from a crash to the attacker running their own code.

How it is reached

Over the internet or network

Access the attacker needs

No account needed

Does the victim have to do something?

Yes, the victim must open or click something

CISA records this vulnerability as known to be used in ransomware campaigns: attackers use it to get in, then encrypt files and demand payment.

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer WebRTC at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

Apply updates per vendor instructions.

Vendor advisories and fixes

• groups.google.comgroups.google.com/g/discuss-webrtc/c/5KBtZx2gvcQ

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on August 25, 2022, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by September 15, 2022, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 70% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 99.4% of all scored vulnerabilities.

Its CVSS severity score is 8.8 out of 10 (high), as recorded in the US National Vulnerability Database.

Technical description

Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.