Vulnerabilities in pkg:golang/github.com/filecoin-project/curio

PACKAGE
Advisory Summary

GHSA-gj6x-q8rh-wj6x is a HIGH curio exposes database credentials to vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Github.com/filecoin project/curio libraries in the Go ecosystem. The issue involves curio exposes database credentials to users with network access through verbose http error responses. Remediation is available by upgrading affected packages to version 1.27.3-rc2.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/filecoin-project/curio

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/filecoin-project/curio. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-gj6x-q8rh-wj6x - HIGH Curio exposes database credentials to users with network access through verbose HTTP error responses

GHSA-gj6x-q8rh-wj6x at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-gj6x-q8rh-wj6x
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Github.com/filecoin project/curio
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-gj6x-q8rh-wj6x

To remediate this vulnerability, upgrade all affected Github.com/filecoin project/curio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/filecoin-project/curio fixed: 1.27.3-rc2
Upgrade github.com/filecoin-project/curio to 1.27.3-rc2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/filecoin-project/curio

How to Check if You Are Affected

To determine whether your application is affected by GHSA-gj6x-q8rh-wj6x, inspect your project dependencies for Github.com/filecoin project/curio:

inspect dependencies for github.com/filecoin-project/curio

Analyze the terminal output to locate any version of Github.com/filecoin project/curio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.27.3-rc2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Github.com/filecoin project/curio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Multiple HTTP handlers in Curio passed raw database error messages to HTTP clients via `http.Error()`. When the PostgreSQL/YugabyteDB driver (pgx) returned errors, these could contain the database connection string — including hostname, port, username, and password. Additionally, the internal connection string was constructed with the plaintext password embedded in the URL, which was also included in startup error messages and could surface in logs. ## Details Three components were affected: 1. **PDP handlers** (`pdp/handlers.go`) — 18+ HTTP error paths passed `err.Error()` directly to HTTP responses. While these endpoints require ECDSA JWT authentication, an authenticated client (e.g., a FilPay service) that triggered a database error would receive the raw pgx error in the HTTP response body. Present since PDP was introduced in v1.25.1. 2. **Market mk12 deal status** (`market/mk12/mk12_utils.go`) — The `GetDealStatus` handler included `err.Error()` in error responses: `"failed to query the db for deal status: %s"`. Present since v1.24.3. 3. **Market mk20 auth middleware** (`market/mk20/http/http.go`) — Authentication error responses included `err.Error()`, potentially leaking database error details during auth flows. Present since v1.27.2. ### Root Cause The database connection string was constructed as: ``` postgresql://username:password@host:port/database?... ``` The plaintext password was embedded directly in the URL. When pgx returned connection or query errors, the error text could contain fragments of this connection string. HTTP handlers forwarded these errors verbatim to clients. ## Impact An attacker with network access to Curio's PDP or Market HTTP endpoints and valid authentication credentials could intentionally trigger database errors (e.g., by sending malformed requests that cause SQL failures) and extract the YugabyteDB connection credentials from the error response. With these credentials, the attacker could directly access the database, which serves as Curio's control plane. Per Curio's [security boundary documentation](https://github.com/filecoin-project/curio/blob/main/documentation/en/design/README.md#security-boundary), these endpoints are expected to be on a trusted network. However, defense-in-depth requires that credentials are never exposed through HTTP responses regardless of network trust assumptions. ## Remediation (PR #919) 1. **Connection string password masking:** The password in the connection string is replaced with `********`. The real password is set separately via `cfg.ConnConfig.Password`, so it never appears in error messages or logs. 2. **HTTP handler sanitization:** All affected handlers now log the detailed error server-side and return a generic error message to the HTTP client. 3. **Error filter (`errFilter`):** A new function in the database layer detects and redacts any error messages containing keywords like "password", "host", "port", or "://" before they can propagate. 4. **Prometheus metrics cleanup:** Database connection metrics that could expose connection details were removed from the metrics endpoint. 5. **Security boundary documentation:** A new section documents what Curio expects operators to secure. ## Resources - Fix: https://github.com/filecoin-project/curio/pull/919 - Patched release: v1.27.3-rc2

GHSA-gj6x-q8rh-wj6x Affected Github.com/filecoin project/curio Versions

1 component(s)
Fixed Versions:
1.27.3-rc2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/filecoin-project/curio
Go
≥ 1.24.3
< 1.27.3-rc2
1.27.3-rc2

References

Frequently Asked Questions

What is GHSA-gj6x-q8rh-wj6x?
GHSA-gj6x-q8rh-wj6x is a security vulnerability in Github.com/filecoin project/curio involving Curio exposes database credentials to users with network access through verbose HTTP error responses under CWE-532: Insertion of Sensitive Information into Log File.
Which Github.com/filecoin project/curio versions are affected?
Affected versions include releases prior to 1.27.3-rc2 across affected packages: github.com/filecoin-project/curio.
What version fixes GHSA-gj6x-q8rh-wj6x?
Upgrading to 1.27.3-rc2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/filecoin-project/curio affected?
Yes, github.com/filecoin-project/curio is affected in releases prior to 1.27.3-rc2. Upgrade your dependency to 1.27.3-rc2 or later.
What CWE is associated with GHSA-gj6x-q8rh-wj6x?
GHSA-gj6x-q8rh-wj6x is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check Go dependencies for GHSA-gj6x-q8rh-wj6x?
Run the dependency tree command: 'inspect dependencies for github.com/filecoin-project/curio'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-gj6x-q8rh-wj6x",
  "modified" : "2026-02-26T22:48:00Z",
  "published" : "2026-02-26T22:48:00Z",
  "aliases" : [ ],
  "summary" : "Curio exposes database credentials to users with network access through verbose HTTP error responses",
  "details" : "## Summary\n\nMultiple HTTP handlers in Curio passed raw database error messages to HTTP clients via `http.Error()`. When the PostgreSQL/YugabyteDB driver (pgx) returned errors, these could contain the database connection string — including hostname, port, username, and password. Additionally, the internal connection string was constructed with the plaintext password embedded in the URL, which was also included in startup error messages and could surface in logs.\n\n## Details\n\nThree components were affected:\n\n1. **PDP handlers** (`pdp/handlers.go`) — 18+ HTTP error paths passed `err.Error()` directly to HTTP responses. While these endpoints require ECDSA JWT authentication, an authenticated client (e.g., a FilPay service) that triggered a database error would receive the raw pgx error in the HTTP response body. Present since PDP was introduced in v1.25.1.\n\n2. **Market mk12 deal status** (`market/mk12/mk12_utils.go`) — The `GetDealStatus` handler included `err.Error()` in error responses: `\"failed to query the db for deal status: %s\"`. Present since v1.24.3.\n\n3. **Market mk20 auth middleware** (`market/mk20/http/http.go`) — Authentication error responses included `err.Error()`, potentially leaking database error details during auth flows. Present since v1.27.2.\n\n### Root Cause\n\nThe database connection string was constructed as:\n```\npostgresql://username:password@host:port/database?...\n```\nThe plaintext password was embedded directly in the URL. When pgx returned connection or query errors, the error text could contain fragments of this connection string. HTTP handlers forwarded these errors verbatim to clients.\n\n## Impact\n\nAn attacker with network access to Curio's PDP or Market HTTP endpoints and valid authentication credentials could intentionally trigger database errors (e.g., by sending malformed requests that cause SQL failures) and extract the YugabyteDB connection credentials from the error response. With these credentials, the attacker could directly access the database, which serves as Curio's control plane.\n\nPer Curio's [security boundary documentation](https://github.com/filecoin-project/curio/blob/main/documentation/en/design/README.md#security-boundary), these endpoints are expected to be on a trusted network. However, defense-in-depth requires that credentials are never exposed through HTTP responses regardless of network trust assumptions.\n\n## Remediation (PR #919)\n\n1. **Connection string password masking:** The password in the connection string is replaced with `********`. The real password is set separately via `cfg.ConnConfig.Password`, so it never appears in error messages or logs.\n\n2. **HTTP handler sanitization:** All affected handlers now log the detailed error server-side and return a generic error message to the HTTP client.\n\n3. **Error filter (`errFilter`):** A new function in the database layer detects and redacts any error messages containing keywords like \"password\", \"host\", \"port\", or \"://\" before they can propagate.\n\n4. **Prometheus metrics cleanup:** Database connection metrics that could expose connection details were removed from the metrics endpoint.\n\n5. **Security boundary documentation:** A new section documents what Curio expects operators to secure.\n\n## Resources\n\n- Fix: https://github.com/filecoin-project/curio/pull/919\n- Patched release: v1.27.3-rc2",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/filecoin-project/curio"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.24.3"
      }, {
        "fixed" : "1.27.3-rc2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.27.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/filecoin-project/curio/security/advisories/GHSA-gj6x-q8rh-wj6x"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/filecoin-project/curio/pull/919"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/filecoin-project/curio/commit/551da78e0123892600d8e6dfe9de7a579055d80b"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/filecoin-project/curio"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/filecoin-project/curio/blob/main/documentation/en/design/README.md#security-boundary"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-209", "CWE-532" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-26T22:48:00Z",
    "nvd_published_at" : null
  }
}