dbcve.org
Flink Stateful FunctionsApplication · Apache

CVE-2023-41834

MEDIUM · 6.1 CVSS v3.1 Published 2023-09-19
Fix available
A fix is available. Upgrade to after 3.2.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of CRLF Sequences in HTTP Headers in Apache Flink Stateful Functions 3.1.0, 3.1.1 and 3.2.0 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via crafted HTTP requests. Attackers could potentially inject malicious content into the HTTP response that is sent to the user's browser. Users should upgrade to Apache Flink Stateful Functions version 3.3.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Flink Stateful Functions versions 3.1.0, 3.1.1, and 3.2.0 fail to properly neutralize Carriage Return (CR) and Line Feed (LF) characters in HTTP headers, allowing remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via crafted HTTP requests.

MitigationUpgrade Apache Flink Stateful Functions to version 3.3.0 or later to remediate the CRLF injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Flink Stateful FunctionsApplication
Affected:>= 3.1.0, <= 3.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache Flink Stateful Functions version
    Locate the deployed Flink Stateful Functions artifacts (JAR files, container image, or build artifacts) and check the version identifier. Common locations: the flink-statefun-*.jar filename, META-INF/MANIFEST.MF inside JARs, pom.xml dependencies, or the runtime service banner on startup.
    Affected if The version is 3.1.0, 3.1.1, or 3.2.0 (any version >= 3.1.0 through <= 3.2.0).
  2. Confirm HTTP server or endpoint module is enabled
    Review the deployment configuration for State Functions HTTP ingress modules. Check configuration files (such as application.yaml, application.properties, or deployment manifests) for entries enabling StateFunHttpAsyncClusterClient, HTTP ingress, or any HTTP endpoint bindings.
    Affected if HTTP server or HTTP endpoint bindings are configured and enabled, exposing the service to HTTP requests.
  3. Inspect HTTP header handling configuration
    Examine the runtime configuration for any custom HTTP header processing rules. Look for settings related to HTTP response header manipulation, header sanitization options, or custom HTTP server implementations that handle response headers.
    Affected if HTTP header handling is active and no explicit CR/LF sanitization is configured on inbound request headers before they are reflected in responses.

A user is affected if their deployed Apache Flink Stateful Functions version falls within 3.1.0 to 3.2.0 and HTTP endpoints are exposed, allowing external HTTP requests to reach the vulnerable header handling code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.2.0
Interim mitigation

Upgrade Apache Flink Stateful Functions to version 3.3.0 or later to remediate the CRLF injection vulnerability.

Recommended fix High confidence

Apache Flink Stateful Functions 3.3.0

  1. Review the release notes for Apache Flink Stateful Functions 3.3.0 to understand any changes
  2. Obtain Apache Flink Stateful Functions version 3.3.0 from the official Apache download sources
  3. Deploy version 3.3.0 in a non-production environment and verify application functionality
  4. Deploy the updated version to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flink Stateful Functions Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41834 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41834 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data