SQL Injection in connect-pg-simple (CVE-2019-15658)
Summary
SQL injection in connect-pg-simple (CVE-2019-15658). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.0.1 or later.
Original description
The description as published by the source.
connect-pg-simple before 6.0.1 allows SQL injection if tableName or schemaName is untrusted data.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2019-15658 was discovered in connect-pg-simple.
In plain terms, it is a flaw that lets attackers send rogue commands to the database.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "connect-pg-simple CVE-2019-15658".
CVE-2019-15658 (connect-pg-simple). Severity: Info. Category: CWE-89.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2019-15658) in connect-pg-simple. In plain words, it is a flaw that lets attackers send rogue commands to the database.
Target versions of connect-pg-simple (see vendor advisory). If running in production, identify exposure immediately.
Severity: Info. Low severity or not yet rated.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-89)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'connect-pg-simple' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
connect-pg-simpleを grep し、稼働しているサービス・バージョンを把握する。 -
5Apply temporary workaround mitigate
If there is no likelihood that the `tableName` or `schemaName` options sent to the constructor could be of an unsanitized nature, then no workaround is needed.パッチが適用されるまでの応急処置として、If there is no likelihood that the
tableNameorschemaNameoptions sent to the constructor could be of an unsanitized nature, then no workaround is needed. を実施。回避策の副作用 (機能低下) を確認した上で。 -
6Apply patch patch
Upgrade connect-pg-simple to 6.0.1ステージング環境で 6.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web snyk.io
- web npmjs.com