CVE-2024-31190
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 · uneditedOut-of-bounds Read vulnerability in Open Networking Foundation (ONF) libfluid (libfluid_msg module). This vulnerability is associated with program routine fluid_msg::of13::MultipartReplyMeterConfig::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 confidenceAn out-of-bounds read vulnerability exists in the fluid_msg::of13::MultipartReplyMeterConfig::unpack routine of libfluid 0.1.0. This vulnerability occurs during OpenFlow 1.3 message parsing when the unpack function reads beyond allocated buffer boundaries, potentially allowing an attacker to read sensitive memory contents by sending specially crafted MultipartReplyMeterConfig messages.
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= 0.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify libfluid msg versionCheck the installed version of the libfluid-msg library by inspecting package manifests, library files, or running 'dpkg -l libfluid-msg' or 'rpm -qi libfluid-msg' depending on your system package managerAffected if The installed version is 0.1.0 exactly
-
Verify OpenFlow 1.3 message parsing is in useReview application logs, configuration, or code that imports or uses the of13 module from libfluid-msg (look for 'fluid_msg::of13' namespace usage in source code or linked binaries)Affected if OpenFlow 1.3 parsing is enabled and the application uses libfluid msg 0.1.0
-
Confirm MultipartReplyMeterConfig message handlingInspect network traffic captures or application debug logs for incoming OpenFlow 1.3 MultipartReply messages with type METER_CONFIG (value 2), or review code that calls unpack() on MultipartReplyMeterConfig objectsAffected if The application processes MultipartReplyMeterConfig messages using the vulnerable unpack routine in version 0.1.0
-
Check for evidence of memory access anomaliesRun the application under memory debugging tools such as AddressSanitizer (ASAN) or Valgrind when processing OpenFlow 1.3 messages, or review system logs for segmentation faults related to libfluid-msgAffected if Memory access violations occur during MultipartReplyMeterConfig message parsing, indicating potential out-of-bounds read exploitation
You are affected if libfluid-msg version 0.1.0 is installed and your application uses OpenFlow 1.3 message parsing with MultipartReplyMeterConfig message handling enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper bounds checking in the MultipartReplyMeterConfig::unpack routine to validate message lengths before reading data. Additionally, apply input validation on all incoming OpenFlow messages to ensure they conform to expected size specifications before processing.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31190 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-31190 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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