GHSA-qqc3-94qv-7fw3: Hubuum client library (Rust) Configured Custom Transports May Be Vulnerability

MODERATE
CWE-693
Published
Advisory Summary

GHSA-qqc3-94qv-7fw3 is a MODERATE configured custom transports may be vulnerability (CWE-693: Protection Mechanism Failure) affecting Hubuum client library (Rust) libraries in the crates.io ecosystem. The issue involves configured custom transports may be bypassed, exposing credentials and network traffic. Remediation is available by upgrading affected packages to version 0.6.1.

GHSA-qqc3-94qv-7fw3 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-qqc3-94qv-7fw3
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-693: Protection Mechanism Failure
Affected Product Hubuum client library (Rust)
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-qqc3-94qv-7fw3

To remediate this vulnerability, upgrade all affected Hubuum client library (Rust) dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

hubuum_client fixed: 0.6.1
Upgrade hubuum_client to 0.6.1
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 hubuum_client

How to Check if You Are Affected

To determine whether your application is affected by GHSA-qqc3-94qv-7fw3, inspect your project dependencies for Hubuum client library (Rust):

inspect dependencies for hubuum_client

Analyze the terminal output to locate any version of Hubuum client library (Rust) in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.6.1), 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-693: Protection Mechanism Failure, where the product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. In Hubuum client library (Rust), 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 When an application configures hubuum_client with ClientBuilder::with_transport, several client operations still use the built-in reqwest client directly. The bypass includes password login, bearer-token validation, authentication-provider discovery, health and readiness probes, export-output downloads, and unified-search streams. ## Impact Applications may use a custom transport as a security boundary for network isolation, proxy enforcement, request signing, audit logging, or policy checks. Affected operations bypass those controls and make direct network requests to the configured base URL. Password login can therefore send plaintext credentials outside the intended transport, while token validation can send a bearer token outside it. Other bypassing calls can evade audit and routing policy. The issue affects custom transports introduced in 0.3.0. Applications that do not configure a custom transport are not affected by the bypass. ## Defense in depth The same private fix disables redirect following for built-in async and blocking clients so an authenticated request remains at the endpoint validated and constructed by the client. Applications supplying a preconfigured reqwest client continue to control its redirect policy. ## Remediation The proposed fix routes authentication, public discovery and probe calls, export downloads, unified-search streams, raw requests, and typed requests through the configured transport in both async and blocking clients. It preserves retry and error-body policies, documents the buffering semantics of custom transports, and surfaces built-in-client redirects as 3xx API errors. ## Validation Regression tests assert async and blocking routing, paths, login bodies, bearer headers, streaming bodies, retries, error handling, and redirect behavior. Formatting, Clippy with warnings denied, rustdoc warnings, the complete workspace suite, all supported feature combinations, Rust 1.88 MSRV, OpenAPI validation, and the combined library plus downstream-consumer integration suites pass against the immutable Hubuum 0.0.3 image.

GHSA-qqc3-94qv-7fw3 Affected Hubuum client library (Rust) Versions

1 component(s)
Fixed Versions:
0.6.1
Product / Package Ecosystem Affected Versions Fixed Version
hubuum_client
crates.io
≥ 0.3.0
< 0.6.1
0.6.1

References

Frequently Asked Questions

What is GHSA-qqc3-94qv-7fw3?
GHSA-qqc3-94qv-7fw3 is a security vulnerability in Hubuum client library (Rust) involving Configured custom transports may be bypassed, exposing credentials and network traffic under CWE-693: Protection Mechanism Failure.
Which Hubuum client library (Rust) versions are affected?
Affected versions include releases prior to 0.6.1 across affected packages: hubuum_client.
What version fixes GHSA-qqc3-94qv-7fw3?
Upgrading to 0.6.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is hubuum_client affected?
Yes, hubuum_client is affected in releases prior to 0.6.1. Upgrade your dependency to 0.6.1 or later.
What CWE is associated with GHSA-qqc3-94qv-7fw3?
GHSA-qqc3-94qv-7fw3 is classified under CWE-693: Protection Mechanism Failure (The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.).
How can I check crates.io dependencies for GHSA-qqc3-94qv-7fw3?
Run the dependency tree command: 'inspect dependencies for hubuum_client'. 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-qqc3-94qv-7fw3",
  "modified" : "2026-07-24T21:49:05Z",
  "published" : "2026-07-24T21:49:05Z",
  "aliases" : [ ],
  "summary" : "Hubuum client library (Rust): Configured custom transports may be bypassed, exposing credentials and network traffic",
  "details" : "## Summary\n\nWhen an application configures hubuum_client with ClientBuilder::with_transport, several client operations still use the built-in reqwest client directly. The bypass includes password login, bearer-token validation, authentication-provider discovery, health and readiness probes, export-output downloads, and unified-search streams.\n\n## Impact\n\nApplications may use a custom transport as a security boundary for network isolation, proxy enforcement, request signing, audit logging, or policy checks. Affected operations bypass those controls and make direct network requests to the configured base URL. Password login can therefore send plaintext credentials outside the intended transport, while token validation can send a bearer token outside it. Other bypassing calls can evade audit and routing policy.\n\nThe issue affects custom transports introduced in 0.3.0. Applications that do not configure a custom transport are not affected by the bypass.\n\n## Defense in depth\n\nThe same private fix disables redirect following for built-in async and blocking clients so an authenticated request remains at the endpoint validated and constructed by the client. Applications supplying a preconfigured reqwest client continue to control its redirect policy.\n\n## Remediation\n\nThe proposed fix routes authentication, public discovery and probe calls, export downloads, unified-search streams, raw requests, and typed requests through the configured transport in both async and blocking clients. It preserves retry and error-body policies, documents the buffering semantics of custom transports, and surfaces built-in-client redirects as 3xx API errors.\n\n## Validation\n\nRegression tests assert async and blocking routing, paths, login bodies, bearer headers, streaming bodies, retries, error handling, and redirect behavior. Formatting, Clippy with warnings denied, rustdoc warnings, the complete workspace suite, all supported feature combinations, Rust 1.88 MSRV, OpenAPI validation, and the combined library plus downstream-consumer integration suites pass against the immutable Hubuum 0.0.3 image.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "hubuum_client"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.3.0"
      }, {
        "fixed" : "0.6.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.6.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/hubuum/hubuum-client-rust/security/advisories/GHSA-qqc3-94qv-7fw3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/hubuum/hubuum-client-rust/commit/5a5c275ffa45f342459b7d3e977926da643bde50"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/hubuum/hubuum-client-rust"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/hubuum/hubuum-client-rust/releases/tag/v0.6.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-693" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-24T21:49:05Z",
    "nvd_published_at" : null
  }
}