dbcve.org
Libfluid MsgApplication · Opennetworking

CVE-2024-31188

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::of13::MultipartReplyTableFeatures::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 · moderate confidence

An out-of-bounds read vulnerability exists in the fluid_msg::of13::MultipartReplyTableFeatures::unpack routine within libfluid_msg module. The vulnerability occurs during parsing of OpenFlow 1.3 MultipartReply Table Features messages, where the unpack function fails to properly validate buffer bounds before reading data, potentially allowing an attacker to read memory outside allocated buffers.

MitigationUpgrade to a patched version of libfluid if available; otherwise, implement proper bounds checking in the MultipartReplyTableFeatures::unpack routine to validate buffer lengths before reading data.

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
    Search for libfluid_msg library files on the system. Common paths include /usr/lib/, /usr/local/lib/, or within project dependencies. Look for files named libfluid_msg.so, libfluid_msg.a, or similar. If using a package manager, query installed packages.
    Affected if The libfluid_msg library is present on the system
  2. Identify installed version
    Check the version of libfluid_msg installed. If via package manager (dpkg, rpm, etc.), query the package. If source-built, check the version.h, CMakeLists.txt, or git tags in the source directory. Compare against the affected version 0.1.0.
    Affected if The installed version is 0.1.0
  3. Confirm OpenFlow 1.3 module is in use
    Inspect the application or service that uses libfluid_msg. Check configuration files or code for references to of13, OpenFlow 1.3, or the MultipartReplyTableFeatures class. This vulnerability exists specifically in the of13 (OpenFlow 1.3) module.
    Affected if OpenFlow 1.3 (of13) support is enabled or used
  4. Verify Table Features parsing is active
    Examine network traffic or logs for OFPT_MULTILPART (type 18) messages with multipart type 12 (OFMPT_TABLE_FEATURES). This is the specific message type that triggers the vulnerable unpack routine in MultipartReplyTableFeatures.
    Affected if The environment processes OpenFlow 1.3 MultipartReply Table Features messages
  5. Inspect vulnerable code routine
    If source code is available, locate the file containing MultipartReplyTableFeatures::unpack (typically in src/of13msg.cc or similar within libfluid_msg). Look for the unpack routine and verify if bounds checking on the buffer parameter occurs before data access.
    Affected if The unpack routine lacks proper buffer length validation before reading data

A system is affected if it runs libfluid_msg version 0.1.0 and processes OpenFlow 1.3 MultipartReply Table Features messages, as the vulnerable MultipartReplyTableFeatures::unpack routine will be invoked without proper bounds checking.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of libfluid if available; otherwise, implement proper bounds checking in the MultipartReplyTableFeatures::unpack routine to validate buffer lengths before reading data.

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-31188 — 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-31188 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