dbcve.org
VeilidApplication

CVE-2023-40711

HIGH · 7.5 CVSS v3.1 Published 2023-08-20
Fix available
A fix is available. Upgrade to 0.1.9 or later.
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
Veilid before 0.1.9 does not check the size of uncompressed data during decompression upon an envelope receipt, which allows remote attackers to cause a denial of service (out-of-memory abort) via crafted packet data, as exploited in the wild in August 2023.

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

Veilid before version 0.1.9 lacks bounds checking on the size of uncompressed data during decompression when processing incoming envelope receipts. An attacker can send crafted packet data with a high compression ratio, causing the decompression to allocate excessive memory until the system aborts due to out-of-memory conditions.

MitigationUpgrade Veilid to version 0.1.9 or later, which implements proper size validation before decompression. Consider implementing network-level rate limiting or packet size limits as additional defense-in-depth.

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
VeilidApplication
Affected:< 0.1.9

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 installed Veilid version
    Run 'veilid-version' or check the version via the API using 'veilid-cli get state' or inspect the binary metadata
    Affected if The version number is less than 0.1.9 (for example, 0.1.8, 0.1.7, etc.)
  2. Verify Veilid is exposed to incoming network traffic
    Check the Veilid configuration file (usually in the application data directory) for 'listen' or 'bind' settings under the network section, or review firewall rules allowing inbound connections to Veilid ports
    Affected if Veilid is configured to accept incoming connections from untrusted network segments
  3. Confirm envelope receipt processing is enabled
    Inspect the Veilid runtime configuration for any settings related to envelope handling, or check if the envelope subsystem is loaded by examining the process startup logs
    Affected if Envelope receipt processing is active (this is typically enabled by default in standard Veilid deployments)
  4. Check for memory exhaustion indicators
    Monitor system memory usage or check Veilid logs for out-of-memory errors or decompression failures occurring during incoming packet processing
    Affected if Memory usage spikes or OOM events coincide with incoming envelope receipt traffic

You are affected if Veilid version is below 0.1.9 and the system processes incoming envelope receipts from network sources.

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
Upgrade available Upgrade to 0.1.9 or later
Fixed in 0.1.9
Interim mitigation

Upgrade Veilid to version 0.1.9 or later, which implements proper size validation before decompression. Consider implementing network-level rate limiting or packet size limits as additional defense-in-depth.

Recommended fix High confidence

Veilid 0.1.9 or later

  1. 1. Identify the current Veilid version installed in your environment
  2. 2. Stop any running Veilid services or processes
  3. 3. Download Veilid version 0.1.9 or later from the official GitLab repository
  4. 4. Install the new version following the official installation instructions
  5. 5. Restart the Veilid service
  6. 6. Verify the new version is running correctly

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

Fix this in Veilid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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