Security readout for executives and security teams
Plain-English summary
A malicious or faulty RRDP repository could keep Routinator waiting by slowly sending small amounts of data. This can stall RPKI validation, leaving routers dependent on old validation data, or no data after startup.
Executive priority
Prioritize remediation for organizations operating RPKI validation infrastructure. This is not described as data theft or code execution, but stale or missing validation data can affect routing trust decisions.
Technical view
Routinator before 0.10.2 applied RRDP timeouts per read or write operation, not to the complete request. A peer could drip-feed bytes before each timeout, delaying repository update completion and blocking the validation run.
Likely exposure
Exposure is limited to NLnet Labs Routinator deployments before 0.10.2 that use RRDP. Impact is mainly availability and data freshness for RPKI validation services.
Exploitation context
The bundle does not show active exploitation or CISA KEV listing. Exploitation requires an RRDP repository that Routinator contacts and that can intentionally keep responses alive.
Researcher notes
The root issue is timeout scope: operation-level timeouts allowed an entire RRDP request to remain open indefinitely through slow incremental data. Evidence does not include CVSS, exploit reports, or detailed fixed-code analysis.
Mitigation direction
- Upgrade Routinator to 0.10.2 or later.
- Apply Debian security updates referenced in DSA-5033 and DSA-5041 where applicable.
- Monitor RPKI validation age and alert on stalled validation runs.
- Review vendor guidance before applying compensating controls beyond patching.
Validation and detection
- Inventory Routinator deployments and identify versions below 0.10.2.
- Confirm whether deployments use RRDP repository updates.
- Review logs for unusually long RRDP updates or stalled validation runs.
- After updating, verify validation completes and current data is served.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-755: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-43173 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.nlnetlabs.nl/downloads/routinator/CVE-2021-43172_CVE-2021-43173_CVE-2021-43174.txtCVE reference · x_refsource_MISC
- DSA-5033CVE reference · vendor-advisory, x_refsource_DEBIAN
- DSA-5041CVE reference · vendor-advisory, x_refsource_DEBIAN
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.