CVE-2017-13783

What it actually does

The flaw allows remote attackers to trigger memory corruption in the WebKit component, enabling arbitrary code execution or denial of service through a crafted web site.

Why it matters to the business

Potential full system compromise or service disruption affecting users of impacted container runtimes and related documentation packages, with low but stable exploit likelihood and available public exploits increasing urgency for patching across ecosystems with many downstream dependents.

How an attack unfolds

An attacker crafts a malicious website that, when visited by a user on an affected system, triggers memory corruption in WebKit leading to code execution or crash; public exploits are available and could be leveraged by threat actors in campaigns.

How to fix it

Update runc (Chainguard) to 1.1.12-r7, runc (Wolfi) to 1.1.12-r7, runc-doc (Chainguard) to 1.1.12-r7, and runc-doc (Wolfi) to 1.1.12-r7. Apply vendor patches promptly given exploit availability.

How to confirm the fix worked

Verify package versions match the fixed releases listed and confirm no vulnerable WebKit components remain in the environment through dependency scans.

Typical attack path

1. Deliver crafted website via phishing or compromised site
2. Victim browser or application processes the malicious content
3. Memory corruption is triggered leading to RCE or DoS
4. Attacker gains code execution or crashes the application

How to detect it

Review web server and browser logs for access to suspicious or crafted URLs; look for sudden application crashes or unexpected code execution patterns in process monitoring.

What your security team should do

• Prioritize patching all listed runc packages to the specified fixed versions within 30 days
• Monitor EPSS and exploit maturity trends for any increase in activity
• Scan for any remaining vulnerable instances across container ecosystems