CVE-2013-5661 json
Cache Poisoning issue exists in DNS Response Rate Limiting.
published 7y ago modified 4mo ago also EUVD-2013-5500
- cvss
- 5.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Cache Poisoning issue exists in DNS Response Rate Limiting.
Patch / fix
- nic knot_resolver 1.3.0
Is CVE-2013-5661 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-5661 updated cvss 2.6
DNS response rate limiting can simplify cache poisoning attacks
-
Red Hat Enterprise Linux 6 bind, bind-sdb, bind-libs, bind-utils, bind-chroot Red Hat Enterprise Linux 7 bind, bind-sdb, bind-libs, bind-utils, bind-chroot, bind-pkcs11, +6 moreaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 5 bind, bind97not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.45% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2013-5661
issue-tracking, third-party-advisory
-
bugzilla.suse.com
/show_bug.cgi?id=CVE-2013-5661
issue-tracking, third-party-advisory
-
security-tracker.debian.org
/tracker/CVE-2013-5661
third-party-advisory
Sources
- CVE List CVE-2013-5661
- NVD CVE-2013-5661
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.