4 Medium
CVSS2
Attack Vector
NETWORK
Attack Complexity
HIGH
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
NONE
AV:N/AC:H/Au:N/C:P/I:P/A:N
6.5 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
LOW
Availability Impact
NONE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
0.001 Low
EPSS
Percentile
46.5%
The uClibc and uClibc-ng libraries, prior to uClibc-ng 1.0.41, are vulnerable to DNS cache poisoning due to the use of predicatble DNS transaction IDs when making DNS requests. This vulnerability can allow an attacker to perform DNS cache poisoning attacks against a vulnerable environment.
The uClibc and the Uclibc-ng software are lightweight C standard libraries intended for use in embedded systems and mobile devices. The uClibc library has not been updated since May of 2012. The newer uClibc-ng is the currently maintained fork of uClibc, as announced on the OpenWRT mailing list in July 2014.
Researchers at the Nozomi Networks Security Research Team discovered that all existing versions of uClibc and uClibc-ng libraries are vulnerable to DNS cache poisoning. These libraries do not employ any randomization in the DNS Transaction ID (DNS TXID) field when creating a new DNS request. This can allow an attacker to send maliciously crafted DNS packets to corrupt the DNS cache with invalid entries and redirect users to arbitrary sites. As uClibc and uClibc-ng are used in devices such as home routers and firewalls, an attacker can perform attacks against multiple users in a shared network environment that relies on DNS responses from the vulnerable device.
The DNS cache poisoning scenarios and defenses are discussed in IETF RFC5452.
The lack of DNS response validation can allow an attacker to use unsolicited DNS responses to poison the DNS cache and redirect users to malicious sites.
If your vendor has developed a patched version of uClibc or uClibc-ng to address this issue, apply the updates provided by your vendor. uClibc-ng was updated to 1.0.41 on 05/20/2022.
If you have a forked or customized version of uClibc or uClibc-ng, develop or adopt a patch to ensure the dns_lookup
function provides adequate randomization of DNS TXID’s while making DNS requests. Review and consider applying the patch has been made available in patchwork repository of uClibc-ng with VU#638879 tag.
Consider the following security best-practices to protect DNS infrastructure:
Thanks to the Nozomi Networks Security Research Team for this report
This document was written by Vijay Sarvepalli and Timur Snoke.
473698
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: March 22, 2022
CVE-2022-30295 | Affected |
---|
We have two active devices using uClibc AND susceptible to this based on version: ConnectCore 9P 9215
ConnectME 9210 We will patch once it is available.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: March 02, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: March 11, 2022
CVE-2022-30295 | Not Affected |
---|
Our products use Glibc instead of UClibc.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: March 21, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: March 16, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: February 10, 2022
CVE-2022-30295 | Not Affected |
---|
All DNS requests made by userland apps go through a DNS caching resolver before beeing sent to the Internet. The DNS caching resolver implements a transaction-ID/source port randomization that is indepent from what was generated by a userland program (whatever c-library it used).
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: February 01, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: May 03, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: April 06, 2022
CVE-2022-30295 | Not Affected |
---|
No Brocade Fibre Channel Products from Broadcom products are currently known to be affected by this vulnerability.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 25, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 26, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 26, 2022
CVE-2022-30295 | Not Affected |
---|
This code is not in our RTOS
Notified: 2022-01-24 Updated: 2023-04-04
Statement Date: April 04, 2023
CVE-2022-30295 | Not Affected |
---|
F5 does not use uClibc or uClibc-ng in any products.
Notified: 2022-01-24 Updated: 2022-05-10
Statement Date: May 10, 2022
CVE-2022-30295 | Not Affected |
---|
I confirmed the use of uClibc to all robot software group. There is no use of it in FANUC Robot Controller
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: May 09, 2022
CVE-2022-30295 | Not Affected |
---|
To the knowledge of our development team, we are not at risk or do not use the afore mentioned components that would create the vulnerability.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: February 07, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: February 01, 2022
CVE-2022-30295 | Not Affected |
---|
HardenedBSD supports neither uClibc nor uClibc-ng.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: May 03, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Not Affected |
---|
uClibc is not in base illumos. Distributions, however, may use them, but a quick survey suggests not in mandatory distribution software.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 25, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Not Affected |
---|
SmartOS (an illumos distribution) is not affected by this issue, nor is our Triton cloud management system.
Notified: 2022-01-24 Updated: 2023-02-22
Statement Date: February 22, 2023
CVE-2022-30295 | Not Affected |
---|
Based on our investigation we confirm that there are no platforms/products which are affected from these vulnerabilities.
Security Incident Response Team Juniper Networks
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-23
Statement Date: May 23, 2022
CVE-2022-30295 | Not Affected |
---|
Dear all,
Moxa is investigating the vulnerability and has determined that none of our products are currently affected. Thank you for the information and notification.
Sincerely, Moxa PSIRT
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 25, 2022
CVE-2022-30295 | Not Affected |
---|
Muonics does not use uClibc or uClibc-ng libraries in any of its products and thus this vulnerability is not applicable.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: March 21, 2022
CVE-2022-30295 | Not Affected |
---|
OpenWrt 19.07 is using uClibc-ng only on Synopsys ARC CPUs, all other targets are using musl libc by default. musl libc and glibc are not affected by this problem. OpenWrt 21.02 and later are not using uClibc-ng or uClibc at all. These versions are not affected by the problem. Synopsys ARC CPUs switched to glibc in OpenWrt 21.02.
OpenWrt 19.07 is end of life since March 2022 and we will not fix this problem in OpenWrt 19.07 or any other version.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: April 04, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: May 03, 2022
CVE-2022-30295 | Not Affected |
---|
No use of uClibc and uClibc-ng in our products.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: April 01, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: May 09, 2022
CVE-2022-30295 | Not Affected |
---|
RTI products don’t use uClibc or uClibc-ng libraries.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Not Affected |
---|
I have checked our SBOM library and we are not vulnerable to this.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: February 10, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-07-06
Statement Date: June 07, 2022
CVE-2022-30295 | Not Affected |
---|
SUSE is not shipping uClibc in any of its current products at this time.
Notified: 2022-05-26 Updated: 2022-05-27
Statement Date: May 27, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-27
Statement Date: May 27, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-06-06
Statement Date: June 03, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-08-29
Statement Date: August 23, 2022
CVE-2022-30295 | Not Affected |
---|
uCLibc was removed from the Ubuntu archives in 2011, and uClibc-ng has never been included in Ubuntu.
Notified: 2022-05-26 Updated: 2022-05-27
Statement Date: May 27, 2022
CVE-2022-30295 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Unknown |
---|
MikroTik RouterOS v7.x.x does not use uClibc
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: May 02, 2022
CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 24, 2022
CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09
Statement Date: January 25, 2022
CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-07-12
Statement Date: July 11, 2022
CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-07-06
Statement Date: June 24, 2022
CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-07-12
Statement Date: July 12, 2022
CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-11-29 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-05-26 Updated: 2022-05-09 CVE-2022-30295 | Unknown |
---|
We have not received a statement from the vendor.
View all 293 vendors __View less vendors __
CVE IDs: | CVE-2022-30295 |
---|---|
API URL: | VINCE JSON |
Date Public: | 2022-05-02 Date First Published: |
astrolavos.gatech.edu/articles/increased_dns_resistance.pdf
en.wikipedia.org/wiki/Secure_by_default
mailman.openadk.org/mailman3/hyperkitty/list/[email protected]/thread/KZD3HQ3MUT63JC3STZ6IH7E7RGQSOV75/
nvd.nist.gov/vuln/detail/CVE-2022-30295
patchwork.ozlabs.org/project/uclibc-ng/list/?state=new
tools.ietf.org/html/rfc5452
uclibc-ng.org/
uclibc.org/
www.kb.cert.org/vuls/id/210620
www.kb.cert.org/vuls/id/252735
www.kb.cert.org/vuls/id/484649
www.kb.cert.org/vuls/id/800113
www.kb.cert.org/vuls/id/927905
www.nozominetworks.com/blog/nozomi-networks-discovers-unpatched-dns-bug-in-popular-c-standard-library-putting-iot-at-risk/
4 Medium
CVSS2
Attack Vector
NETWORK
Attack Complexity
HIGH
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
NONE
AV:N/AC:H/Au:N/C:P/I:P/A:N
6.5 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
LOW
Availability Impact
NONE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
0.001 Low
EPSS
Percentile
46.5%