dbcve.org
Libfluid MsgApplication · Opennetworking

CVE-2024-31180

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::GroupDesc::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

Out-of-bounds read vulnerability in the fluid_msg::of13::GroupDesc::unpack function of libfluid 0.1.0. This parsing routine reads beyond allocated buffer boundaries when processing OpenFlow 1.3 GroupDesc messages, potentially allowing unauthenticated attackers to read sensitive memory contents via specially crafted network packets.

MitigationGiven libfluid appears to be an abandoned project (version 0.1.0), remediation requires either patching the unpack function with proper bounds validation, migrating to an active fork, or replacing the library entirely. Until fixed, restrict network access to OpenFlow controllers using libfluid.

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 if libfluid library is in use
    Search for libfluid in project dependencies (e.g., check package.json, requirements.txt, Cargo.toml, pom.xml, or similar dependency manifests) or search for 'libfluid' or 'fluid_msg' strings in the codebase
    Affected if libfluid is present in the project's dependencies or source code
  2. Verify the exact version of libfluid
    Check the dependency version specification. For npm: check package.json for 'libfluid' or 'fluid-msg'. For Python: check requirements.txt or setup.py. For Rust: check Cargo.toml. For Java: check pom.xml or build.gradle
    Affected if The version is listed as exactly 0.1.0 or if the version cannot be determined but libfluid is present
  3. Confirm OpenFlow 1.3 protocol support is enabled
    Search configuration files or code for OpenFlow 1.3 enablement flags, OF13, OF_1.3, or 'of13' module imports. Check controller configuration for 'protocol-version' set to 1.3 or 'openflow' version settings
    Affected if OpenFlow 1.3 (OF 1.3) support is enabled in the controller or switch configuration
  4. Determine if GroupDesc message processing is active
    Review logs for GroupDesc request/response handling, or search code for 'GroupDesc', 'group_desc', 'OFPT_GROUP_DESC_STATS' or 'ofp_group_desc_stats' references. Check if the controller processes group statistics
    Affected if The application processes or handles OpenFlow GroupDesc messages (OFPGT_GROUP type statistics)
  5. Check for direct exposure to untrusted network traffic
    Verify network accessibility of the OpenFlow controller port (default 6653/6633). Review firewall rules and network segmentation around the controller. Determine if the controller accepts connections from untrusted or external network segments
    Affected if The OpenFlow controller port is accessible from untrusted network segments or the internet

You are affected if libfluid version 0.1.0 is in use, OpenFlow 1.3 is enabled, and the controller is exposed to untrusted network paths that can send crafted GroupDesc messages.

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

Given libfluid appears to be an abandoned project (version 0.1.0), remediation requires either patching the unpack function with proper bounds validation, migrating to an active fork, or replacing the library entirely. Until fixed, restrict network access to OpenFlow controllers using libfluid.

Fix this in Libfluid Msg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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