dbcve.org
Libfluid MsgApplication · Opennetworking

CVE-2024-31167

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
Unchecked Return Value to NULL Pointer Dereference vulnerability in Open Networking Foundation (ONF) libfluid (libfluid_msg module). This vulnerability is associated with program routine fluid_msg::QueuePropertyList::unpack13. 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

A NULL pointer dereference vulnerability exists in libfluid_msg's QueuePropertyList::unpack13 routine where an unchecked return value leads to dereferencing a NULL pointer. This occurs when the routine fails to validate the return value from a function call before using it, potentially causing a denial of service or undefined behavior when processing queue property list messages.

MitigationImplement proper return value validation in the QueuePropertyList::unpack13 routine to ensure all function return values are checked before use, particularly before dereferencing pointers.

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. Identify libfluid_msg installation and version
    Locate the libfluid_msg library in your environment and check its version. Common methods: grep for version files, check package manager listings, or inspect library binary metadata. Look for version indicator 0.1.0.
    Affected if libfluid_msg version 0.1.0 is installed in the environment
  2. Verify QueuePropertyList class usage
    Search project source code or dependencies for references to QueuePropertyList class and specifically the unpack13 method. This may appear in message handling or OpenFlow controller code.
    Affected if Code uses QueuePropertyList::unpack13 routine to process queue property list messages
  3. Check for queue property list message processing
    Monitor or review application logs and code paths that handle OpenFlow queue property list messages. Inspect any packet/message parsing routines that process queue-related OpenFlow messages.
    Affected if The application processes queue property list messages that trigger the unpack13 routine path

The environment is affected if libfluid_msg version 0.1.0 is installed AND code paths that call QueuePropertyList::unpack13 to process queue property list messages are exercised.

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

Implement proper return value validation in the QueuePropertyList::unpack13 routine to ensure all function return values are checked before use, particularly before dereferencing pointers.

Recommended fix Moderate confidence

Upgrade to the patched release of libfluid_msg that includes the fix for CVE-2024-31167 (check ONF libfluid official releases)

  1. 1. Identify the current libfluid_msg version in use by reviewing project dependencies (e.g., in CMakeLists.txt, package.json, or requirements.txt)
  2. 2. Locate all code paths that call fluid_msg::QueuePropertyList::unpack13
  3. 3. Upgrade libfluid_msg to a version that addresses CVE-2024-31167. Check the official ONF libfluid repository or release notes for the patched version
  4. 4. After upgrading, recompile and rebuild the project to ensure the new library version is linked
  5. 5. Test the QueuePropertyList functionality to verify the unpack13 method works correctly and no NULL pointer dereference occurs
  6. 6. Run existing test suites to ensure no regressions were introduced by the upgrade
Caveat Review release notes for any API changes or backward incompatibilities between version 0.1.0 and the patched version

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

Fix this in Libfluid Msg Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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