pg is vulnerable to SQL Injection
59
CVE Score
Medium
SQL Injection
PG::Connection#set_client_encoding passes the caller supplied encoding name into a command sent to the PostgreSQL backend. When an application forwards a user controlled or externally influenced encoding value to this method, unescaped SQL metacharacters in that value reach the backend as part of the command, so unexpected SQL executes on the connection. The patch stops building that command from the raw unvalidated argument.
Upgrade the pg library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you pass a user controlled or externally influenced value to set_client_encoding.
0.7.9.2008.01.28 - 1.6.3
Fixed in 1.7.0pg is vulnerable to SQL Injection in versions 0.7.9.2008.01.28 - 1.6.3.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.