Get Started
- CodeAnt AI
- Setup
- Control Center
- Pull Request Review
- IDE
- Compliance
- Anti-Patterns
- Code Governance
- Infrastructure Security Database
- Application Security Database
- Apex
- Bash
- C
- Clojure
- Cpp
- Csharp
- Dockerfile
- Elixir
- Fingerprints
- Generic
- Go
- Aws-lambda
- Gin
- Gorilla
- Gorm
- Grpc
- Jwt-go
- Lang
- Net
- Active-debug-code
- Command-injection
- Csrf
- Dos
- Nosql
- Path-traversal
- Sql
- Go-vanillasql-format-string-sqli-taint-med-conf
- Go-vanillasql-format-string-sqli-taint
- Pg-orm-sqli-taint
- Pg-sqli-taint-med-conf
- Pg-sqli-taint
- Pgx-sqli-taint-med-conf
- Pgx-sqli-taint
- Ssrf
- Xss
- Xxe
- Otto
- Secrets
- Template
- Html
- Java
- Javascript
- Json
- Kotlin
- Ocaml
- Php
- Problem-based-packs
- Python
- Ruby
- Rust
- Scala
- Solidity
- Swift
- Terraform
- Typescript
- Yaml
Pgx-sqli-taint
Pgx sqli taint
Untrusted input might be used to build a database query, which can lead to a SQL injection vulnerability. An attacker can execute malicious SQL statements and gain unauthorized access to sensitive data, modify, delete data, or execute arbitrary system commands. Create parameterized queries in pgx by using positional parameters ($1, $2, …) and adding the values as additional arguments to the function call. It is also possible to create prepared statements through the Prepare function. This function uses the same placeholders for bound parameters.
Likelihood: HIGH
Confidence: HIGH
CWE:
- CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)
OWASP:
- A01:2017 - Injection
- A03:2021 - Injection