CVE-2020-17446: Critical severity Magic Asyncpg vulnerability
asyncpg before 0.21.0 allows a malicious PostgreSQL server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, because of access to an uninitialized pointer in the array data decoder.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/asyncpgto a version that resolves this vulnerability.Fixed in 0.21.0 - Upgrade
Upgrade
ubuntu/asyncpgto a version that resolves this vulnerability.Fixed in 0.13.0-1ubuntu3+esm1 - Upgrade
Upgrade
ubuntu/asyncpgto a version that resolves this vulnerability.Fixed in 0.20.0-1ubuntu0.1~esm1
Event History
Frequently Asked Questions
What is the severity of CVE-2020-17446?
CVE-2020-17446 is categorized as a critical vulnerability due to its potential to execute arbitrary code.
How do I fix CVE-2020-17446?
To fix CVE-2020-17446, upgrade asyncpg to version 0.21.0 or later.
What is the impact of CVE-2020-17446 on PostgreSQL?
CVE-2020-17446 allows a malicious PostgreSQL server to crash or execute arbitrary code on the database client.
Which versions of asyncpg are affected by CVE-2020-17446?
CVE-2020-17446 affects asyncpg versions prior to 0.21.0.
Who is affected by CVE-2020-17446?
Users of asyncpg versions before 0.21.0 who connect to untrusted PostgreSQL servers are at risk from CVE-2020-17446.