GHSA-f45q-w629-wr25: Hubuum client library (Rust) Authenticated Requests May Escape The Vulnerability

MODERATE
CWE-200
Published
Advisory Summary

GHSA-f45q-w629-wr25 is a MODERATE authenticated requests may escape the vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Hubuum client library (Rust) libraries in the crates.io ecosystem. The issue involves authenticated requests may escape the configured base path through redirects. Remediation is available by upgrading affected packages to version 0.6.1.

GHSA-f45q-w629-wr25 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-f45q-w629-wr25
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Hubuum client library (Rust)
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-f45q-w629-wr25

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-f45q-w629-wr25, 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-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. 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

## Impact The built-in async and blocking clients used reqwest's default redirect policy. `BaseUrl` constrains the initial request to the configured origin and path prefix, but redirect processing occurs after that validation. reqwest retains sensitive headers when a redirect changes only the path on the same scheme, host, and port. A redirect from a Hubuum endpoint to another path on a shared origin could therefore carry the bearer `Authorization` header outside the configured Hubuum path prefix. Exploitation requires an attacker, compromised server, or intermediary to influence a 3xx response. Cross-origin redirects are not affected because reqwest strips sensitive headers when scheme, host, or port changes. ## Patches Version 0.6.1 configures both built-in HTTP clients with `reqwest::redirect::Policy::none()`. Redirect responses are returned as 3xx API errors instead of being followed. Supplying a preconfigured reqwest client remains an explicit opt-in to that client's redirect policy. ## Workarounds On affected versions, construct a reqwest client with `reqwest::redirect::Policy::none()` and pass it through `with_http_client`. Deployments can also reduce exposure by ensuring the Hubuum origin is not shared with other applications and that trusted infrastructure never redirects API requests outside the configured path prefix.

GHSA-f45q-w629-wr25 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.0.1
< 0.6.1
0.6.1

References

Frequently Asked Questions

What is GHSA-f45q-w629-wr25?
GHSA-f45q-w629-wr25 is a security vulnerability in Hubuum client library (Rust) involving Authenticated requests may escape the configured base path through redirects under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
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-f45q-w629-wr25?
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-f45q-w629-wr25?
GHSA-f45q-w629-wr25 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check crates.io dependencies for GHSA-f45q-w629-wr25?
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-f45q-w629-wr25",
  "modified" : "2026-07-24T21:48:36Z",
  "published" : "2026-07-24T21:48:36Z",
  "aliases" : [ ],
  "summary" : "Hubuum client library (Rust): Authenticated requests may escape the configured base path through redirects",
  "details" : "## Impact\n\nThe built-in async and blocking clients used reqwest's default redirect policy. `BaseUrl` constrains the initial request to the configured origin and path prefix, but redirect processing occurs after that validation. reqwest retains sensitive headers when a redirect changes only the path on the same scheme, host, and port. A redirect from a Hubuum endpoint to another path on a shared origin could therefore carry the bearer `Authorization` header outside the configured Hubuum path prefix.\n\nExploitation requires an attacker, compromised server, or intermediary to influence a 3xx response. Cross-origin redirects are not affected because reqwest strips sensitive headers when scheme, host, or port changes.\n\n## Patches\n\nVersion 0.6.1 configures both built-in HTTP clients with `reqwest::redirect::Policy::none()`. Redirect responses are returned as 3xx API errors instead of being followed. Supplying a preconfigured reqwest client remains an explicit opt-in to that client's redirect policy.\n\n## Workarounds\n\nOn affected versions, construct a reqwest client with `reqwest::redirect::Policy::none()` and pass it through `with_http_client`. Deployments can also reduce exposure by ensuring the Hubuum origin is not shared with other applications and that trusted infrastructure never redirects API requests outside the configured path prefix.",
  "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.0.1"
      }, {
        "fixed" : "0.6.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/hubuum/hubuum-client-rust/security/advisories/GHSA-f45q-w629-wr25"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/hubuum/hubuum-client-rust/commit/5a5c275ffa45f342459b7d3e977926da643bde50"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/hubuum/hubuum-client-rust"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-24T21:48:36Z",
    "nvd_published_at" : null
  }
}