dbcve.org
KrillApplication · Nlnetlabs

CVE-2023-0158

HIGH · 7.5 CVSS v3.1 Published 2023-01-17
Fix available
A fix is available. Upgrade to 0.12.1 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
NLnet Labs Krill supports direct access to the RRDP repository content through its built-in web server at the "/rrdp" endpoint. Prior to 0.12.1 a direct query for any existing directory under "/rrdp/", rather than an RRDP file such as "/rrdp/notification.xml" as would be expected, causes Krill to crash. If the built-in "/rrdp" endpoint is exposed directly to the internet, then malicious remote parties can cause the publication server to crash. The repository content is not affected by this, but the availability of the server and repository can cause issues if this attack is persistent and is not mitigated.

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

Krill's built-in web server crashes when receiving requests for directories under '/rrdp/' rather than specific RRDP files like 'notification.xml'. This is a denial-of-service vulnerability in versions prior to 0.12.1 where malformed RRDP requests cause the publication server to crash.

MitigationUpgrade to Krill 0.12.1 or later. If immediate upgrade is not feasible, ensure the '/rrdp' endpoint is not directly exposed to the internet via firewall or network access controls.

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
KrillApplication
Affected:< 0.12.1

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. Check if Krill is installed
    Look for the Krill binary on the system or check running processes for Krill.
    Affected if Krill is installed and running on the system.
  2. Determine the installed Krill version
    Run 'krill --version' or 'krill -V' from the command line to retrieve the version number.
    Affected if The version returned is lower than 0.12.1.
  3. Verify the web server is enabled
    Inspect the Krill configuration file for web server settings, or check if the HTTP/HTTPS port is listening.
    Affected if The web server is enabled and configured to accept connections.
  4. Confirm RRDP endpoint accessibility
    Attempt to access the /rrdp/ directory path via HTTP request to the Krill server.
    Affected if The /rrdp/ endpoint responds to directory requests, indicating the server may crash when malformed requests are sent.

If Krill version is below 0.12.1 and the web server with RRDP endpoint is exposed, the system is vulnerable to this denial-of-service flaw.

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.12.1 or later
Fixed in 0.12.1
Interim mitigation

Upgrade to Krill 0.12.1 or later. If immediate upgrade is not feasible, ensure the '/rrdp' endpoint is not directly exposed to the internet via firewall or network access controls.

Recommended fix High confidence

0.12.1

  1. 1. Check current Krill version by running `krillc version` or inspecting the running container/process
  2. 2. Backup your Krill configuration and data directory before upgrading
  3. 3. Upgrade Krill to version 0.12.1 or later using your package manager or deployment method (e.g., `cargo install krill --version 0.12.1`, or your container orchestrator pull the new image)
  4. 4. Restart the Krill service to apply the upgrade
  5. 5. Verify the new version is running: `krillc version`
  6. 6. Confirm the /rrdp endpoint no longer crashes when accessing directory paths

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

Fix this in Krill Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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