GHSA-c7jm-38gq-h67h: http4k `ServerFilters.DigestAuth` / `DigestAuthProvider` Defaulted To Vulnerability

MODERATE
Share
CWE-294
Published
Advisory Summary

GHSA-c7jm-38gq-h67h is a MODERATE `serverfilters.digestauth` / `digestauthprovider` defaulted to vulnerability (CWE-294: Authentication Bypass by Capture-replay) affecting http4k libraries in the Maven ecosystem. The issue involves `serverfilters.digestauth` / `digestauthprovider` defaulted to an always-true nonce verifier, disabling replay protection in default deployments. Remediation is available by upgrading affected packages to version 6.48.0.0, 5.42.0.0, 4.51.0.0.

GHSA-c7jm-38gq-h67h at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-c7jm-38gq-h67h
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-294: Authentication Bypass by Capture-replay
Affected Product http4k
Package Ecosystem Maven
Published Date
Last Updated

How to Fix GHSA-c7jm-38gq-h67h

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

org.http4k:http4k-security-digest fixed: 6.48.0.0 
<dependency>
    <groupId>org.http4k</groupId>
    <artifactId>http4k-security-digest</artifactId>
    <version>6.48.0.0</version>
</dependency>
org.http4k:http4k-security-digest fixed: 5.42.0.0 
<dependency>
    <groupId>org.http4k</groupId>
    <artifactId>http4k-security-digest</artifactId>
    <version>5.42.0.0</version>
</dependency>
org.http4k:http4k-security-digest fixed: 4.51.0.0 
<dependency>
    <groupId>org.http4k</groupId>
    <artifactId>http4k-security-digest</artifactId>
    <version>4.51.0.0</version>
</dependency>
Verify Direct and Transitive Dependencies

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

mvn dependency:tree -Dincludes=org.http4k

How to Check if You Are Affected

To determine whether your Java application is affected by GHSA-c7jm-38gq-h67h, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.http4k

Analyze the terminal output to locate any version of http4k in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.48.0.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.http4k command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-294: Authentication Bypass by Capture-replay, where a capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). In http4k, 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 `ServerFilters.DigestAuth` and the underlying `DigestAuthProvider` both defaulted their `nonceVerifier` parameter to `{ true }` — i.e. every nonce was accepted regardless of value, age, or prior use. Any deployment using the default configuration had **no replay protection** on Digest authentication; a captured `Authorization: Digest …` response could be replayed indefinitely against the same protected resource. The nonce-verification mechanism in Digest auth is the primary anti-replay control — without it, Digest reduces to a credential bound only to a stale nonce string. **Who is affected:** any application using `ServerFilters.DigestAuth` or `DigestAuthProvider` with the default `nonceVerifier`. The broken default has been present since `DigestAuthProvider` was introduced (2021). Exploitation requires the attacker to first capture a valid Digest response (network observation, log access, etc.) — non-trivial in modern TLS deployments but not impossible. Anyone running Digest auth with default config should treat upgrade as urgent. ### Patches | Line | Fixed in | Edition | |------|----------|---------| | v6.x (Community) | **6.48.0.0** | Community | | v5.x (LTS) | **5.42.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if Digest auth is present in your v5.x line) | | v4.x (LTS) | **4.51.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if Digest auth is present in your v4.x line) | The fix (`[Break]`) removes the default value for `nonceVerifier` from both `ServerFilters.DigestAuth` and `DigestAuthProvider`. Callers must now supply a real verifier explicitly — the broken default cannot be silently inherited. ### Workarounds For deployments that cannot upgrade immediately: explicitly supply a `nonceVerifier` that tracks issued nonces, enforces a TTL, and rejects re-use. Do not rely on the default.

GHSA-c7jm-38gq-h67h Affected http4k Versions

3 component(s)
Fixed Versions:
6.48.0.05.42.0.04.51.0.0
Product / Package Ecosystem Affected Versions Fixed Version
org.http4k:http4k-security-digest
maven/org.http4k/http4k-security-digest
Maven
≥ 6.0.0.0
< 6.48.0.0
6.48.0.0
org.http4k:http4k-security-digest
maven/org.http4k/http4k-security-digest
Maven
≥ 5.0.0.0
< 5.42.0.0
5.42.0.0
org.http4k:http4k-security-digest
maven/org.http4k/http4k-security-digest
Maven
< 4.51.0.0
4.51.0.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/http4k/http4k/security/advisories/GHSA-c7jm-38gq-h67h
Security Fix Commit FIX COMMIT
https://github.com/http4k/http4k/commit/4f904b4692
Security Fix Commit FIX COMMIT
https://github.com/http4k/http4k/commit/8a52b615b1
datatracker.ietf.org/doc/html/rfc7616 WEB
https://datatracker.ietf.org/doc/html/rfc7616#section-3.4
http4k Source Repository REPOSITORY
https://github.com/http4k/http4k
http4k Release RELEASE
https://github.com/http4k/http4k/releases/tag/6.48.0.0

Frequently Asked Questions

What is GHSA-c7jm-38gq-h67h?
GHSA-c7jm-38gq-h67h is a security vulnerability in http4k involving `ServerFilters.DigestAuth` / `DigestAuthProvider` defaulted to an always-true nonce verifier, disabling replay protection in default deployments under CWE-294: Authentication Bypass by Capture-replay.
Which http4k versions are affected?
Affected versions include releases prior to 6.48.0.0, 5.42.0.0, 4.51.0.0 across affected packages: org.http4k:http4k-security-digest.
What version fixes GHSA-c7jm-38gq-h67h?
Upgrading to 6.48.0.0, 5.42.0.0, 4.51.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is http4k-security-digest affected?
Yes, org.http4k:http4k-security-digest is affected in releases prior to 6.48.0.0, 5.42.0.0, 4.51.0.0. Upgrade your dependency to 6.48.0.0, 5.42.0.0, 4.51.0.0 or later.
What CWE is associated with GHSA-c7jm-38gq-h67h?
GHSA-c7jm-38gq-h67h is classified under CWE-294: Authentication Bypass by Capture-replay (A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).).
How can I check Maven dependencies for GHSA-c7jm-38gq-h67h?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.http4k'. 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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c7jm-38gq-h67h",
  "modified" : "2026-06-19T21:16:09Z",
  "published" : "2026-06-19T21:16:09Z",
  "aliases" : [ ],
  "summary" : "http4k: `ServerFilters.DigestAuth` / `DigestAuthProvider` defaulted to an always-true nonce verifier, disabling replay protection in default deployments",
  "details" : "### Impact\n\n`ServerFilters.DigestAuth` and the underlying `DigestAuthProvider` both defaulted their `nonceVerifier` parameter to `{ true }` — i.e. every nonce was accepted regardless of value, age, or prior use. Any deployment using the default configuration had **no replay protection** on Digest authentication; a captured `Authorization: Digest …` response could be replayed indefinitely against the same protected resource.\n\nThe nonce-verification mechanism in Digest auth is the primary anti-replay control — without it, Digest reduces to a credential bound only to a stale nonce string.\n\n**Who is affected:** any application using `ServerFilters.DigestAuth` or `DigestAuthProvider` with the default `nonceVerifier`. The broken default has been present since `DigestAuthProvider` was introduced (2021). Exploitation requires the attacker to first capture a valid Digest response (network observation, log access, etc.) — non-trivial in modern TLS deployments but not impossible. Anyone running Digest auth with default config should treat upgrade as urgent.\n\n### Patches\n\n| Line | Fixed in | Edition |\n|------|----------|---------|\n| v6.x (Community) | **6.48.0.0** | Community |\n| v5.x (LTS) | **5.42.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if Digest auth is present in your v5.x line) |\n| v4.x (LTS) | **4.51.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if Digest auth is present in your v4.x line) |\n\nThe fix (`[Break]`) removes the default value for `nonceVerifier` from both `ServerFilters.DigestAuth` and `DigestAuthProvider`. Callers must now supply a real verifier explicitly — the broken default cannot be silently inherited.\n\n### Workarounds\n\nFor deployments that cannot upgrade immediately: explicitly supply a `nonceVerifier` that tracks issued nonces, enforces a TTL, and rejects re-use. Do not rely on the default.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4k:http4k-security-digest"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0.0.0"
      }, {
        "fixed" : "6.48.0.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4k:http4k-security-digest"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0.0"
      }, {
        "fixed" : "5.42.0.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4k:http4k-security-digest"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.51.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/http4k/http4k/security/advisories/GHSA-c7jm-38gq-h67h"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4k/http4k/commit/4f904b4692"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4k/http4k/commit/8a52b615b1"
  }, {
    "type" : "WEB",
    "url" : "https://datatracker.ietf.org/doc/html/rfc7616#section-3.4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/http4k/http4k"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4k/http4k/releases/tag/6.48.0.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-294" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T21:16:09Z",
    "nvd_published_at" : null
  }
}