PatchTheCVEdproxy-nexgen vulnerabilities and fixes
Recent CVEs affecting dproxy-nexgen, with upgrade or downgrade steps. 4 tracked.
Also searched as: dproxy nexgen.
dproxy-nexgen has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2022-08-15. Highest priority: CVE-2022-33990 (score 53/100).
- CVE-2022-33991 MEDIUM 5.3 MITIGATE dproxy-nexgen (aka dproxy nexgen) forwards and caches DNS queries with the CD (aka checking disabled) bit set
- CVE-2022-33990 HIGH 7.5 MITIGATE Misinterpretation of special domain name characters in dproxy-nexgen (aka dproxy nexgen) leads to cache poison
- CVE-2022-33989 MEDIUM 5.3 MITIGATE dproxy-nexgen (aka dproxy nexgen) uses a static UDP source port (selected randomly only at boot time) in upstr
- CVE-2022-33988 HIGH 7.5 MITIGATE dproxy-nexgen (aka dproxy nexgen) re-uses the DNS transaction id (TXID) value from client queries, which allow
FAQ
How do I fix dproxy-nexgen vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is dproxy-nexgen being exploited right now?
None of the tracked dproxy-nexgen CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which dproxy-nexgen CVE should I patch first?
CVE-2022-33990 currently ranks highest (53/100): Misinterpretation of special domain name characters in dproxy-nexgen (aka dproxy nexgen) leads to cache poison.