Debian LinuxOperating system · Debian
CVE-2021-3910
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 · uneditedOctoRPKI crashes when encountering a repository that returns an invalid ROA (just an encoded NUL (\0) character).
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 confidenceOctoRPKI crashes when processing an invalid ROA (Route Origin Authorization) containing only an encoded NUL character. This is a denial-of-service vulnerability in the ROA parsing logic that causes the application to terminate unexpectedly when a malicious or misconfigured RPKI repository serves malformed 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
Debian LinuxOperating system
= 11.0< 1.4.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.
-
Check if OctoRPKI is installedOn Debian systems, run 'dpkg -l | grep -i octorpki' or check for the binary at /usr/bin/octorpki or /usr/local/bin/octorpkiAffected if OctoRPKI package or binary is present on the system
-
Determine the installed OctoRPKI versionRun 'octorpki --version' or 'dpkg -s octorpki' to retrieve the package versionAffected if Version is less than 1.4.0 for Cloudflare Octorpki, or the package is from Debian 11.0
-
Verify if RPKI ROA processing is enabledCheck the running configuration or process for active RPKI repository URLs being processed. Look for command-line arguments or config files specifying RPKI trust anchors and ROA fetchingAffected if OctoRPKI is configured to fetch and process ROAs from RPKI repositories
-
Confirm the application is processing live RPKI dataReview logs or running processes to confirm OctoRPKI is actively connecting to RPKI repositories (typically on TCP port 323)Affected if The application is actively fetching and parsing ROA objects from remote RPKI servers
The environment is affected if OctoRPKI is installed with a version prior to 1.4.0 and is actively configured to process ROA data from RPKI repositories.
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.
dbcve · scoped1.4.0
Upgrade OctoRPKI to the patched version that handles malformed ROA input gracefully. Implement network-level filtering to validate RPKI data sources before processing.
Octorpki >= 1.4.0 (or fixed Debian package for version 11)
- Check current OctoRPKI version installed: dpkg -l | grep octorpki or octorpki --version
- Update package lists: apt-get update
- Upgrade OctoRPKI to version 1.4.0 or later: apt-get install octorpki
- Verify the fixed version is installed: dpkg -l | grep octorpki or octorpki --version
- Test that OctoRPKI no longer crashes on invalid ROA input
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation1.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3910 — 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-2021-3910 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