Skip to main content
MediumDNSOWASP A02:2021CWE-326

How to fix: DNSSEC RSA key below 2048 bits

A published DNSKEY uses an RSA algorithm with a modulus smaller than 2048 bits. That is below the floor RFC 8624 sets for DNSSEC signing keys; the size is read from the RFC 3110 public-key blob in the record.

Why it matters

An undersized signing key is the weakest link in the chain of trust regardless of how strong the hash is. Forging a signature over any record in the zone lets an attacker who can reach a validating resolver answer with data of their own choosing, which is exactly the substitution DNSSEC exists to prevent.

A 1024-bit key-signing key is the more serious of the two cases, because it is the key the DS record at the registrar commits to and it typically has a much longer lifetime than a zone-signing key. Moving to ECDSAP256SHA256 solves the size problem and shrinks responses at the same time, which matters for a protocol that still has to fit into UDP wherever it can.

How to fix it

  1. 1Roll the affected key to at least 2048-bit RSA, or move the zone to ECDSAP256SHA256.
  2. 2If the key-signing key is the one affected, coordinate the rollover with the registrar so the DS record is updated in step.
  3. 3Set a key-rollover schedule rather than treating this as a one-time fix.

Code examples

Read the key sizes

bash
dig +multi DNSKEY example.com @1.1.1.1
# dnssec-keygen -a ECDSAP256SHA256 -f KSK example.com  # replacement KSK

References

Detected automatically by VulnRadar. The check id is dns-dnssec-key-size-weak, stable across every scan so you can filter or diff on it.

See every dns check

Questions

How severe is DNSSEC RSA key below 2048 bits?
VulnRadar rates this medium severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id dns-dnssec-key-size-weak, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does DNSSEC RSA key below 2048 bits map to?
It maps to CWE-326. In the OWASP Top 10 it falls under A02:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for dnssec rsa key below 2048 bits

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: DNSSEC RSA key below 2048 bits | VulnRadar