CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
Percentile
48.9%
The Heimdal Software Kerberos 5 implementation is vulnerable to a null pointer dereferance. An attacker with network access to an application that depends on the vulnerable code path can cause the application to crash.
CVE-2022-3116 A flawed logical condition in lib/gssapi/spnego/accept_sec_context.c allows a malicious actor to remotely trigger a NULL pointer dereference using a crafted negTokenInit token.
An attacker can use a specially crafted network packet to cause a vulnerable application to crash.
The latest version of code in the Heimdal master branch fixes the issue. However, the current stable release 7.7.0 does not include the fix.
Thanks to Internet Systems Consortium for reporting the vulnerability.
This document was written by Kevin Stephens.
730793
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Notified: 2021-06-22 Updated: 2022-10-07
Statement Date: June 22, 2021
CVE-2022-3116 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07
Statement Date: June 22, 2021
CVE-2022-3116 | Affected |
---|
Though HardenedBSD is affected, it is not possible to create a memory allocation at the 0 (NULL) address in HardenedBSD. Thus, at its worst, this bug will crash the application.
Notified: 2021-06-22 Updated: 2022-12-19 CVE-2022-3116 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: February 10, 2022
CVE-2022-3116 | Not Affected |
---|
Heimdal ist not in use within our products or our organisation.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: February 02, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: March 14, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: April 06, 2022
CVE-2022-3116 | 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-10-07
Statement Date: February 02, 2022
CVE-2022-3116 | Not Affected |
---|
We do not distribute the code for gssapi spnego
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: August 22, 2022
CVE-2022-3116 | Not Affected |
---|
Cradlepoint conducted a review of their offerings and the lib/gssapi/spnego/accept_sec_context.c library is not used in any of our products.
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: August 26, 2022
CVE-2022-3116 | Not Affected |
---|
Heimdal is not in use in dd-wrt. In contrary to openwrt, dd-wrt uses ksmbd instead of samba4.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
DT is not reusing heimdal code in our branded products and is not affected.
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: October 05, 2022
CVE-2022-3116 | Not Affected |
---|
Digi’s platforms, infrastructure, and or services disallows kerberos/gssapi authentication from any available service and does not appear vulnerable to this exploit.
Notified: 2022-01-24 Updated: 2023-01-12
Statement Date: December 27, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 26, 2022
CVE-2022-3116 | Not Affected |
---|
Code not used in our RTOS
Notified: 2022-01-24 Updated: 2023-07-13
Statement Date: July 03, 2023
CVE-2022-3116 | Not Affected |
---|
No F5 products or services use the affected Heimdal functionality.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: March 01, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
We do not use Heimdal in base illumos for our GSSAPI. Because the report’s conditions state:
> It is believed that any binary which fulfills both of the following conditions:
>
> * it is linked to an affected version of the Heimdal libgssapi library
> * it allows SPNEGO to be used
>
> is vulnerable to the attack described below.
illumos should not be affected. illumos users should contact [email protected] if they notice GSSAPI issues, however.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 31, 2022
CVE-2022-3116 | Not Affected |
---|
Verified Heimdal not used by Intel.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 25, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
We do not use Heimdal in base illumos for our GSSAPI, nor in any base SmartOS or Triton pkgsrc packages. (Optional pkgsrc packages may be affected, but these are on a per package basis.) Because the report’s conditions state:
> It is believed that any binary which fulfills both of the following conditions:
>
> * it is linked to an affected version of the Heimdal libgssapi library
> * it allows SPNEGO to be used
>
> is vulnerable to the attack described below.
SmartOS and Triton should not be affected. SmartOS users should contact [email protected] if they notice GSSAPI issues (as they would be with illumos), however.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: September 21, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: February 04, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 25, 2022
CVE-2022-3116 | Not Affected |
---|
Muonics does not use Heimdal in any of its products and thus this vulnerability is not applicable.
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: September 13, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 26, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: March 29, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: June 07, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-09-13 Updated: 2022-11-09
Statement Date: October 31, 2022
CVE-2022-3116 | Not Affected |
---|
Per Samba’s bugzilla https://bugzilla.samba.org/show_bug.cgi?id=15204
https://samba-team.gitlab.io/samba/third_party/heimdal/lib/gssapi/spnego/index.html shows we don’t run the Heimdal SPNEGO code.
Samba doesn’t use Heimdal for SPNEGO, we handle the SPNEGO in GENSEC, not in Heimdal.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: March 01, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 27, 2022
CVE-2022-3116 | Not Affected |
---|
SUSE is not shipping the heimdal krb5 implementation.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 24, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: April 06, 2022
CVE-2022-3116 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: August 23, 2022
CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: August 24, 2022
CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: August 25, 2022
CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07
Statement Date: January 25, 2022
CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-06-22 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-11-09
Statement Date: August 19, 2022
CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2022-01-24 Updated: 2022-10-07 CVE-2022-3116 | Unknown |
---|
We have not received a statement from the vendor.
View all 246 vendors __View less vendors __
CVE IDs: | CVE-2022-3116 |
---|---|
API URL: | VINCE JSON |
Date Public: | 2022-10-07 Date First Published: |