dbcve.org
Libfluid MsgApplication · Opennetworking

CVE-2024-31169

HIGH · 7.5 CVSS v3.1 Published 2024-09-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Out-of-bounds Read vulnerability in Open Networking Foundation (ONF) libfluid (libfluid_msg module). This vulnerability is associated with program routine fluid_msg::of10::QueueGetConfigReply::unpack. This issue affects libfluid: 0.1.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

Out-of-bounds read vulnerability in libfluid_msg module's QueueGetConfigReply::unpack routine (OpenFlow 1.0). The vulnerability allows reading memory outside allocated buffer boundaries when parsing QueueGetConfigReply messages, potentially exposing sensitive memory contents.

MitigationUpdate libfluid to a patched version if available; otherwise, implement explicit bounds checking in the QueueGetConfigReply::unpack routine before accessing buffer data and validate message length fields against expected structures.

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
Libfluid MsgApplication
Affected:= 0.1.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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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. Locate libfluid_msg library in the environment
    Search for libfluid_msg library files in common system paths (/usr/lib/, /usr/local/lib/) or within project dependencies. Check dependency manifests (package.json, requirements.txt, Cargo.toml, go.mod) if this is an application using the library.
    Affected if libfluid_msg library is present in the system or project dependencies
  2. Identify installed version of libfluid_msg
    Query the package manager for libfluid_msg version, check library file metadata, or review version information in dependency lock files. Compare the found version against the affected version (0.1.0).
    Affected if Installed version is 0.1.0 exactly
  3. Confirm OpenFlow 1.0 protocol support is enabled
    Review application configuration files and runtime settings for OpenFlow 1.0 (OF10) enablement flags, controller settings, or switch configuration that specifies OpenFlow version 1.0.
    Affected if OpenFlow 1.0 protocol support is enabled in the controller or switch configuration
  4. Determine if QueueGetConfigReply messages are processed
    Examine application code or logs for handling of OFPT_QUEUE_GET_CONFIG_REPLY messages (OpenFlow 1.0 Queue Get Config Reply). This is a specific message type used in OpenFlow 1.0 for querying queue configurations.
    Affected if Application processes QueueGetConfigReply messages from switches or controllers

Environment is affected if libfluid_msg version 0.1.0 is present AND OpenFlow 1.0 is enabled with active QueueGetConfigReply message processing.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libfluid to a patched version if available; otherwise, implement explicit bounds checking in the QueueGetConfigReply::unpack routine before accessing buffer data and validate message length fields against expected structures.

Recommended fix High confidence
  1. No vendor-supplied patch or fixed version is available for this vulnerability.
  2. Libfluid (including libfluid_msg) is largely unmaintained; consider migrating to a maintained OpenFlow library or controller framework.
  3. If continued use is required, implement input validation around QueueGetConfigReply message parsing to prevent out-of-bounds reads.
  4. Apply network segmentation to limit exposure of OpenFlow control plane traffic to untrusted entities.
Caveat No direct upgrade path exists; libfluid 0.1.0 is the latest release and the project is unmaintained

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

Fix this in Libfluid Msg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31169 — 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-2024-31169 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