CVE-2017-7087

What it actually does

Memory corruption in WebKit allows remote attackers to execute arbitrary code or trigger denial of service via crafted web content.

Why it matters to the business

Older systems remain exposed to potential remote compromise or service disruption when users access malicious websites, though widespread exploitation is not observed.

How an attack unfolds

An attacker crafts a malicious website that triggers the WebKit memory corruption flaw; when a victim visits the site using an affected browser or application, the flaw is triggered leading to code execution or crash. No named threat actors or ransomware campaigns are associated with this issue.

How to fix it

Upgrade aws-flb-kinesis (Chainguard) to 1.10.2-r7, aws-flb-kinesis (Wolfi) to 1.10.2-r7, aws-flb-kinesis-compat (Chainguard) to 1.10.2-r7, and aws-flb-kinesis-compat (Wolfi) to 1.10.2-r7. Apply vendor updates for any dependent WebKit components.

How to confirm the fix worked

Verify installed package versions match the fixed releases listed above and confirm no vulnerable WebKit instances remain in the environment.

Typical attack path

1. Craft malicious HTML/JavaScript content targeting WebKit
2. Host or embed the payload on a website
3. Lure victim to visit the site via phishing or compromised page
4. Victim's browser renders the content triggering memory corruption
5. Attacker gains arbitrary code execution or causes application crash

How to detect it

Search application and system logs for WebKit-related crashes or memory errors following web browsing activity; review process execution after visiting untrusted sites.

What your security team should do

• Prioritize updating the listed packages to the specified fixed versions
• Review browser and application update policies for any lingering legacy WebKit usage
• Monitor EPSS trends and KEV status for changes in exploitation likelihood