BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-27289High confidence

pgx SQL Injection via Line Comment Creation

jackc · pgx

Official source article: GitHub GHSA-M7WR-2XF7-CM9P ↗. Check the applicable product and release in the original source.

8.1HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 12 Jun 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.85% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs jackc pgx and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegolang-github-jackc-pgxVendor fix publishedDebian records a fixed source-package version for this release.4.18.1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcegolang-github-jackc-pgxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcegolang-github-jackc-pgxVendor fix publishedDebian records a fixed source-package version for this release.4.18.1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcegolang-github-jackc-pgxVendor fix publishedDebian records a fixed source-package version for this release.4.18.1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-github-jackc-pgxUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/jackc/pgxSEMVER: introduced 0; fixed 4.18.24.18.2OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/jackc/pgx/v4SEMVER: introduced 0; fixed 4.18.24.18.2OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/jackc/pgx< 4.18.24.18.2GitHub advisory ↗upstream repository advisory · 15 Mar 2026
gogithub.com/jackc/pgx/v4< 4.18.24.18.2GitHub advisory ↗upstream repository advisory · 15 Mar 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-27289 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypgx: SQL Injection via Line Comment Creation
29 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • multicluster-engine/agent-service-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/assisted-installer-agent-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/assisted-installer-rhel8 as a component of Multicluster Engine for Kubernetes
  • advanced-cluster-security/rhacs-central-db-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • advanced-cluster-security/rhacs-rhel8-operator as a component of Red Hat Advanced Cluster Security 3
  • advanced-cluster-security/rhacs-roxctl-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • aap-cloud-ui-container as a component of Red Hat Ansible Automation Platform 2
  • osbuild-composer as a component of Red Hat Enterprise Linux 10
  • osbuild-composer-core as a component of Red Hat Enterprise Linux 10
  • osbuild-composer-worker as a component of Red Hat Enterprise Linux 10
  • osbuild-composer.src as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in pgx. SQL injection can occur when all of the following conditions are met in versions before 4.18.2 of pgx. - The non-default simple protocol is used - A placeholder for a numeric value must be immediately preceded by a minus - There must be a second placeholder for a string value after the first placeholder - Both must be on the same line - Both parameter values must be user-controlled
Remediation
If you are using an earlier version of RHACS 4.3, you are advised to upgrade to patch release 4.3.5.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-0962

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

pgx is a PostgreSQL driver and toolkit for Go. Prior to version 4.18.2, SQL injection can occur when all of the following conditions are met: the non-default simple protocol is used; a placeholder for a numeric value must be immediately preceded by a minus; there must be a second placeholder for a string value after the first placeholder; both must be on the same line; and both parameter values must be user-controlled. The problem is resolved in v4.18.2. As a workaround, do not use the simple protocol or do not place a minus directly before a placeholder.

What

pgx is a PostgreSQL driver and toolkit for Go. Prior to version 4.18.2, SQL injection can occur when all of the following conditions are met: the non-default simple protocol is used; a placeholder for a numeric value must be immediately preceded by a minus; there must be a second placeholder for a string value after the first placeholder; both must be on the same line; and both parameter values must be user-controlled. The problem is resolved in v4.18.2. As a workaround, do not use the simple protocol or do not place a minus directly before a placeholder.

Why

Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

pgx is a PostgreSQL driver and toolkit for Go. Prior to version 4.18.2, SQL injection can occur when all of the following conditions are met: the non-default simple protocol is used; a placeholder for a numeric value must be immediately preceded by a minus; there must be a second placeholder for a string value after the first placeholder; both must be on the same line; and both parameter values must be user-controlled. The problem is resolved in v4.18.2. As a workaround, do not use the simple protocol or do not place a minus directly before a placeholder.

Why

Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-89 ↗

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-89Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-0626Red Hat Enterprise Linux: Mehrere Schwachstellen ermöglichen Manipulation von Dateien

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um Dateien zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240313Security Bulletin 13 Mar 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 13 Mar 2024, published on 13 March 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2024-24785 Référence CVE CVE-2024-24786 https://www.cve.org/CVERecord?id=CVE-2024-24786 Référence CVE CVE-2024-24787 https://www.cve.org/CVERecord?id=CVE-2024-24787 Référence CVE CVE-2024-24789 https://www.cve.org/CVERecord?id=CVE-2024-24789 Référence CVE CVE-2024-24790 https://www.cve.org/CVERecord?id=CVE-2024-24790 Référence CVE CVE-2024-24791 https://www.cve.org/CVERecord?id=CVE-2024-24791 Référence CVE CVE-2024-2511 https://www.cve.org/CVERecord?id=CVE-2024-2511 Référence CVE CVE-2024-25710 https://www.cve.org/CVERecord?id=CVE-2024-25710 Référence CVE CVE-2024-26308 https://www.cve.org/CVERecord?id=CVE-2024-26308 Référence CVE CVE-2024-27289 https://www.cve.org/CVERecord?id=CVE-2024-27289 Référence CVE CVE-2024-27304 https://www.cve.org/CVERecord?id=CVE-2024-27304 Référence CVE CVE-2024-28085 https://www.cve.org/CVERecord?id=CVE-2024-28085 Référence CVE CVE-2024-29018 https://www.cve.org/CVERecord?id=CVE-2024-29018 Référence CVE CVE-2024-29025 https://www.cve.org/CVERecord?id=CVE-2024-29025 Référence CVE CVE-2024-34155 https://www.cve.org/CVERecord?id=CVE-2024-34155 Référence CVE CVE-2024-34156 https://www.cve.org/CVERecord?id=CVE-2024-34156 Référence CVE CVE-2024-34158 https://www.cve.org/CVERecord?id=CVE-2024-34158 Référence CVE CVE-2024-40635 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0562Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2024-21144 Référence CVE CVE-2024-21145 https://www.cve.org/CVERecord?id=CVE-2024-21145 Référence CVE CVE-2024-21208 https://www.cve.org/CVERecord?id=CVE-2024-21208 Référence CVE CVE-2024-21210 https://www.cve.org/CVERecord?id=CVE-2024-21210 Référence CVE CVE-2024-21217 https://www.cve.org/CVERecord?id=CVE-2024-21217 Référence CVE CVE-2024-21235 https://www.cve.org/CVERecord?id=CVE-2024-21235 Référence CVE CVE-2024-21534 https://www.cve.org/CVERecord?id=CVE-2024-21534 Référence CVE CVE-2024-2511 https://www.cve.org/CVERecord?id=CVE-2024-2511 Référence CVE CVE-2024-27267 https://www.cve.org/CVERecord?id=CVE-2024-27267 Référence CVE CVE-2024-27289 https://www.cve.org/CVERecord?id=CVE-2024-27289 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-52900 https://www.cve.org/CVERecord?id=CVE-2024-52900 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2025-1302 https://www.cve.org/CVERecord?id=CVE-2025-1302 Référence CVE CVE-2025-1991 https://www.cve.org/CVERecord?id=CVE-2025-1991 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0514Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-22354 Référence CVE CVE-2024-23081 https://www.cve.org/CVERecord?id=CVE-2024-23081 Référence CVE CVE-2024-23082 https://www.cve.org/CVERecord?id=CVE-2024-23082 Référence CVE CVE-2024-23672 https://www.cve.org/CVERecord?id=CVE-2024-23672 Référence CVE CVE-2024-23807 https://www.cve.org/CVERecord?id=CVE-2024-23807 Référence CVE CVE-2024-24549 https://www.cve.org/CVERecord?id=CVE-2024-24549 Référence CVE CVE-2024-24557 https://www.cve.org/CVERecord?id=CVE-2024-24557 Référence CVE CVE-2024-24786 https://www.cve.org/CVERecord?id=CVE-2024-24786 Référence CVE CVE-2024-25026 https://www.cve.org/CVERecord?id=CVE-2024-25026 Référence CVE CVE-2024-27289 https://www.cve.org/CVERecord?id=CVE-2024-27289 Référence CVE CVE-2024-27306 https://www.cve.org/CVERecord?id=CVE-2024-27306 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29131 https://www.cve.org/CVERecord?id=CVE-2024-29131 Référence CVE CVE-2024-29133 https://www.cve.org/CVERecord?id=CVE-2024-29133 Référence CVE CVE-2024-29180 https://www.cve.org/CVERecord?id=CVE-2024-29180 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-029557pgx project の Go 用 pgx における SQL インジェクションの脆弱性

pgx project の Go 用 pgx には、SQL インジェクションの脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 6 Mar 2024 · Last source change 12 Jun 2025, 15:45 UTC · CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-0962
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 4.18.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 4.18.2 · Fixed: If you are using an earlier version of RHACS 4.3, you are advised to upgrade to patch release 4.3.5.
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-27289 · cve.blacktree.nl