Search for packages
| purl | pkg:deb/debian/openssl@1.1.1w-0%2Bdeb11u1 |
| Next non-vulnerable version | 3.0.16-1~deb12u1 |
| Latest non-vulnerable version | 3.5.0-2 |
| Risk | 3.4 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-2bxp-9qmt-aaar
Aliases: CVE-2024-5535 |
Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application. The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists). This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available. |
Affected by 2 other vulnerabilities. Affected by 1 other vulnerability. Affected by 0 other vulnerabilities. |
|
VCID-44qv-nzwp-b7ed
Aliases: CVE-2024-13176 |
openssl: Timing side-channel in ECDSA signature computation |
Affected by 2 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-6uk8-2jnu-aaam
Aliases: CVE-2024-4741 |
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use. The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use. While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. |
Affected by 2 other vulnerabilities. |
|
VCID-jm31-c3d3-aaap
Aliases: CVE-2024-0727 GHSA-9v9h-cgj8-h64p |
openssl: denial of service via null dereference |
Affected by 2 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 2 other vulnerabilities. |
|
VCID-kc39-vfd3-aaad
Aliases: CVE-2023-5678 |
Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters. Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q. An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate(). Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue. |
Affected by 3 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 2 other vulnerabilities. |
|
VCID-yr2h-w72w-aaab
Aliases: CVE-2024-2511 |
Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue. |
Affected by 2 other vulnerabilities. |
|
VCID-z5js-c6pd-yybd
Aliases: CVE-2024-9143 |
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. |
Affected by 2 other vulnerabilities. Affected by 1 other vulnerability. Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-2bxp-9qmt-aaar | Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application. The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists). This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available. |
CVE-2024-5535
|
| VCID-2rtj-nbth-aaam | Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue. |
CVE-2023-3817
|
| VCID-5khv-27u8-aaaa | AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p). |
CVE-2022-2097
GHSA-3wx7-46ch-7rq2 VC-OPENSSL-20220705-CVE-2022-2097 |
| VCID-5kqm-99x8-aaak | Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length. However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue. |
CVE-2023-3446
|
| VCID-6uk8-2jnu-aaam | Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use. The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use. While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. |
CVE-2024-4741
|
| VCID-9wtx-9sbn-aaam | Vulnerable OpenSSL included in cryptography wheels |
CVE-2023-0286
GHSA-x4qr-2fvf-3mr5 |
| VCID-ec3y-aejm-aaad | The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue. |
CVE-2022-4450
GHSA-v5w6-wcm8-jm4q |
| VCID-jm31-c3d3-aaap | openssl: denial of service via null dereference |
CVE-2024-0727
GHSA-9v9h-cgj8-h64p |
| VCID-kc39-vfd3-aaad | Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters. Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q. An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate(). Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue. |
CVE-2023-5678
|
| VCID-kn8m-m9v4-aaaa | Improper Certificate Validation The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications. |
CVE-2023-0466
|
| VCID-mu8w-emsy-aaak | Improper Certificate Validation Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks. Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether. Policy processing is disabled by default but can be enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. |
CVE-2023-0465
|
| VCID-tkv7-cnhy-aaas | Improper Certificate Validation A security vulnerability has been identified in all supported versions of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems. Policy processing is disabled by default but can be enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. |
CVE-2023-0464
|
| VCID-ur7f-5ey8-aaak | A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. |
CVE-2022-4304
GHSA-p52g-cm5j-mjv4 |
| VCID-uua4-ygek-aaah | The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected. |
CVE-2023-0215
GHSA-r7jw-wp68-3xch |
| VCID-w17h-u8wd-aaaj | In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). |
CVE-2022-2068
VC-OPENSSL-20220621-CVE-2022-2068 |
| VCID-xda1-h5nv-aaaf | Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow. Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service. An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods. When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*). With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms. Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data. Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low. In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature. The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication. In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low. |
CVE-2023-2650
|
| VCID-yr2h-w72w-aaab | Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue. |
CVE-2024-2511
|
| VCID-yrx6-rcrr-aaap | The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). |
CVE-2022-1292
VC-OPENSSL-20220503-CVE-2022-1292 |
| VCID-z5js-c6pd-yybd | Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. |
CVE-2024-9143
|
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2025-06-22T07:55:13.082273+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | None | 36.1.3 |
| 2025-06-22T05:58:25.767889+00:00 | Debian Importer | Fixing | VCID-mu8w-emsy-aaak | None | 36.1.3 |
| 2025-06-21T22:22:53.926370+00:00 | Debian Importer | Affected by | VCID-2bxp-9qmt-aaar | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-21T22:11:35.020966+00:00 | Debian Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 36.1.3 |
| 2025-06-21T21:14:06.671087+00:00 | Debian Importer | Fixing | VCID-5kqm-99x8-aaak | None | 36.1.3 |
| 2025-06-21T21:11:28.024835+00:00 | Debian Importer | Affected by | VCID-z5js-c6pd-yybd | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-21T19:17:19.151130+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.3 |
| 2025-06-21T19:08:13.767981+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.3 |
| 2025-06-21T19:04:26.136124+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.3 |
| 2025-06-21T18:36:29.225477+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.3 |
| 2025-06-21T18:24:00.300265+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.3 |
| 2025-06-21T18:23:50.052681+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.3 |
| 2025-06-21T18:23:37.363363+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.3 |
| 2025-06-21T17:53:27.743735+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T16:39:54.903909+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 36.1.3 |
| 2025-06-21T16:39:21.884716+00:00 | Debian Importer | Affected by | VCID-6uk8-2jnu-aaam | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-21T16:22:13.899677+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T15:25:29.919878+00:00 | Debian Oval Importer | Fixing | VCID-kn8m-m9v4-aaaa | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T15:12:28.092815+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T14:44:03.776780+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 36.1.3 |
| 2025-06-21T14:36:28.743430+00:00 | Debian Oval Importer | Fixing | VCID-mu8w-emsy-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T14:33:38.418287+00:00 | Debian Oval Importer | Fixing | VCID-uua4-ygek-aaah | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T13:24:10.301565+00:00 | Debian Oval Importer | Fixing | VCID-xda1-h5nv-aaaf | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T12:45:30.049261+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T12:16:10.400434+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T11:53:01.296383+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T11:35:48.840790+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.3 |
| 2025-06-21T09:31:48.047665+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 36.1.3 |
| 2025-06-21T09:22:37.463932+00:00 | Debian Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 36.1.3 |
| 2025-06-21T08:46:39.538145+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | None | 36.1.3 |
| 2025-06-21T08:46:36.848994+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | None | 36.1.3 |
| 2025-06-21T08:21:50.550171+00:00 | Debian Oval Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 36.1.3 |
| 2025-06-21T08:21:49.827946+00:00 | Debian Oval Importer | Fixing | VCID-mu8w-emsy-aaak | None | 36.1.3 |
| 2025-06-21T08:21:49.090514+00:00 | Debian Oval Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 36.1.3 |
| 2025-06-21T08:21:48.382278+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 36.1.3 |
| 2025-06-21T07:31:14.852968+00:00 | Debian Oval Importer | Fixing | VCID-uua4-ygek-aaah | None | 36.1.3 |
| 2025-06-21T07:29:58.561009+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | None | 36.1.3 |
| 2025-06-21T07:29:27.627231+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 36.1.3 |
| 2025-06-21T07:28:44.624255+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 36.1.3 |
| 2025-06-21T07:27:08.067235+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | None | 36.1.3 |
| 2025-06-21T05:16:38.445573+00:00 | Debian Oval Importer | Fixing | VCID-w17h-u8wd-aaaj | None | 36.1.3 |
| 2025-06-21T03:37:00.715702+00:00 | Debian Importer | Affected by | VCID-yr2h-w72w-aaab | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-21T03:14:54.121833+00:00 | Debian Oval Importer | Fixing | VCID-yrx6-rcrr-aaap | None | 36.1.3 |
| 2025-06-21T00:47:39.902923+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-20T22:43:44.317483+00:00 | Debian Importer | Affected by | VCID-jm31-c3d3-aaap | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-20T21:52:09.348881+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 36.1.3 |
| 2025-06-20T21:26:23.354904+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 36.1.3 |
| 2025-06-20T21:04:58.336848+00:00 | Debian Importer | Affected by | VCID-44qv-nzwp-b7ed | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-06-08T12:42:47.826874+00:00 | Debian Oval Importer | Fixing | VCID-w17h-u8wd-aaaj | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T12:39:15.351386+00:00 | Debian Oval Importer | Fixing | VCID-kn8m-m9v4-aaaa | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T12:25:21.913811+00:00 | Debian Oval Importer | Fixing | VCID-uua4-ygek-aaah | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T12:24:56.950943+00:00 | Debian Oval Importer | Fixing | VCID-xda1-h5nv-aaaf | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T12:22:49.521430+00:00 | Debian Oval Importer | Fixing | VCID-mu8w-emsy-aaak | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T11:46:07.166789+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T11:37:15.753829+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T11:33:36.434506+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T11:06:45.874340+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T10:54:41.001035+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T10:54:31.114409+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T10:54:19.678163+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.1.0 |
| 2025-06-08T10:25:16.275466+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T09:08:20.246720+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T08:20:02.954461+00:00 | Debian Oval Importer | Fixing | VCID-kn8m-m9v4-aaaa | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T08:06:12.637413+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T07:29:35.550080+00:00 | Debian Oval Importer | Fixing | VCID-mu8w-emsy-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T07:26:41.556853+00:00 | Debian Oval Importer | Fixing | VCID-uua4-ygek-aaah | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T06:18:20.404268+00:00 | Debian Oval Importer | Fixing | VCID-xda1-h5nv-aaaf | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T05:40:48.405390+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T05:20:33.252250+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T05:05:51.905798+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T04:53:59.518870+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.1.0 |
| 2025-06-08T02:32:55.835496+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | None | 36.1.0 |
| 2025-06-08T02:32:52.542987+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | None | 36.1.0 |
| 2025-06-08T02:03:11.217815+00:00 | Debian Oval Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 36.1.0 |
| 2025-06-08T02:03:10.515647+00:00 | Debian Oval Importer | Fixing | VCID-mu8w-emsy-aaak | None | 36.1.0 |
| 2025-06-08T02:03:09.809011+00:00 | Debian Oval Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 36.1.0 |
| 2025-06-08T02:03:09.079209+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 36.1.0 |
| 2025-06-08T01:11:03.959865+00:00 | Debian Oval Importer | Fixing | VCID-uua4-ygek-aaah | None | 36.1.0 |
| 2025-06-08T01:09:44.853270+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | None | 36.1.0 |
| 2025-06-08T01:09:13.222454+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 36.1.0 |
| 2025-06-08T01:08:30.506380+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 36.1.0 |
| 2025-06-08T01:06:54.163338+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | None | 36.1.0 |
| 2025-06-07T22:54:12.807984+00:00 | Debian Oval Importer | Fixing | VCID-w17h-u8wd-aaaj | None | 36.1.0 |
| 2025-06-07T20:47:51.318837+00:00 | Debian Oval Importer | Fixing | VCID-yrx6-rcrr-aaap | None | 36.1.0 |
| 2025-04-13T02:26:29.196696+00:00 | Debian Oval Importer | Affected by | VCID-2bxp-9qmt-aaar | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:26:22.155018+00:00 | Debian Oval Importer | Affected by | VCID-jm31-c3d3-aaap | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:26:17.189509+00:00 | Debian Oval Importer | Affected by | VCID-z5js-c6pd-yybd | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:26:12.315156+00:00 | Debian Oval Importer | Affected by | VCID-yr2h-w72w-aaab | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:26:07.411308+00:00 | Debian Oval Importer | Affected by | VCID-kc39-vfd3-aaad | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:26:05.227248+00:00 | Debian Oval Importer | Affected by | VCID-6uk8-2jnu-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:21:23.054184+00:00 | Debian Oval Importer | Fixing | VCID-yr2h-w72w-aaab | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:21:22.287683+00:00 | Debian Oval Importer | Fixing | VCID-kc39-vfd3-aaad | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:21:20.803502+00:00 | Debian Oval Importer | Fixing | VCID-jm31-c3d3-aaap | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:21:20.017374+00:00 | Debian Oval Importer | Fixing | VCID-z5js-c6pd-yybd | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:21:19.228373+00:00 | Debian Oval Importer | Fixing | VCID-2bxp-9qmt-aaar | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-13T02:21:18.474505+00:00 | Debian Oval Importer | Fixing | VCID-6uk8-2jnu-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T19:41:28.805900+00:00 | Debian Oval Importer | Fixing | VCID-yrx6-rcrr-aaap | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T18:29:36.440665+00:00 | Debian Oval Importer | Fixing | VCID-w17h-u8wd-aaaj | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T18:25:57.339674+00:00 | Debian Oval Importer | Fixing | VCID-kn8m-m9v4-aaaa | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T18:11:30.380780+00:00 | Debian Oval Importer | Fixing | VCID-uua4-ygek-aaah | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T18:11:04.333148+00:00 | Debian Oval Importer | Fixing | VCID-xda1-h5nv-aaaf | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T18:08:51.526609+00:00 | Debian Oval Importer | Fixing | VCID-mu8w-emsy-aaak | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T17:30:59.503052+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T17:21:50.660507+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T17:18:02.966206+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T16:50:07.907891+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T16:37:13.567742+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T16:37:03.329153+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T16:36:51.043078+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | https://www.debian.org/security/oval/oval-definitions-bullseye.xml.bz2 | 36.0.0 |
| 2025-04-12T16:06:22.404907+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T07:40:10.665803+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T06:51:23.560884+00:00 | Debian Oval Importer | Fixing | VCID-kn8m-m9v4-aaaa | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T06:38:15.780646+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T06:02:23.813110+00:00 | Debian Oval Importer | Fixing | VCID-mu8w-emsy-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T05:59:32.304953+00:00 | Debian Oval Importer | Fixing | VCID-uua4-ygek-aaah | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T04:50:36.316819+00:00 | Debian Oval Importer | Fixing | VCID-xda1-h5nv-aaaf | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T04:12:29.973123+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T03:51:35.771491+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T03:36:47.020578+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T03:25:10.293107+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | https://www.debian.org/security/oval/oval-definitions-buster.xml.bz2 | 36.0.0 |
| 2025-04-08T01:00:21.391795+00:00 | Debian Oval Importer | Fixing | VCID-5kqm-99x8-aaak | None | 36.0.0 |
| 2025-04-08T01:00:18.634203+00:00 | Debian Oval Importer | Fixing | VCID-2rtj-nbth-aaam | None | 36.0.0 |
| 2025-04-08T00:35:02.224552+00:00 | Debian Oval Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 36.0.0 |
| 2025-04-08T00:35:01.455384+00:00 | Debian Oval Importer | Fixing | VCID-mu8w-emsy-aaak | None | 36.0.0 |
| 2025-04-08T00:35:00.711893+00:00 | Debian Oval Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 36.0.0 |
| 2025-04-08T00:34:59.949965+00:00 | Debian Oval Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 36.0.0 |
| 2025-04-07T23:43:41.694382+00:00 | Debian Oval Importer | Fixing | VCID-uua4-ygek-aaah | None | 36.0.0 |
| 2025-04-07T23:42:19.860292+00:00 | Debian Oval Importer | Fixing | VCID-ec3y-aejm-aaad | None | 36.0.0 |
| 2025-04-07T23:41:46.869910+00:00 | Debian Oval Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 36.0.0 |
| 2025-04-07T23:41:03.508408+00:00 | Debian Oval Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 36.0.0 |
| 2025-04-07T23:39:23.702019+00:00 | Debian Oval Importer | Fixing | VCID-5khv-27u8-aaaa | None | 36.0.0 |
| 2025-04-07T21:26:12.275999+00:00 | Debian Oval Importer | Fixing | VCID-w17h-u8wd-aaaj | None | 36.0.0 |
| 2025-04-07T19:18:20.502294+00:00 | Debian Oval Importer | Fixing | VCID-yrx6-rcrr-aaap | None | 36.0.0 |
| 2025-04-07T08:03:58.631033+00:00 | Debian Importer | Fixing | VCID-2rtj-nbth-aaam | None | 36.0.0 |
| 2025-04-06T19:35:20.033802+00:00 | Debian Importer | Fixing | VCID-ec3y-aejm-aaad | None | 36.0.0 |
| 2025-04-06T01:32:22.513527+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | None | 36.0.0 |
| 2025-04-05T23:46:29.289156+00:00 | Debian Importer | Fixing | VCID-mu8w-emsy-aaak | None | 36.0.0 |
| 2025-04-05T18:23:14.995731+00:00 | Debian Importer | Affected by | VCID-2bxp-9qmt-aaar | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-05T18:12:03.809343+00:00 | Debian Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 36.0.0 |
| 2025-04-05T17:14:55.082625+00:00 | Debian Importer | Fixing | VCID-5kqm-99x8-aaak | None | 36.0.0 |
| 2025-04-05T17:12:19.827822+00:00 | Debian Importer | Affected by | VCID-z5js-c6pd-yybd | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-05T13:04:18.392942+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 36.0.0 |
| 2025-04-05T13:03:42.289070+00:00 | Debian Importer | Affected by | VCID-6uk8-2jnu-aaam | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-05T11:16:05.416173+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 36.0.0 |
| 2025-04-05T06:48:40.505904+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 36.0.0 |
| 2025-04-05T06:39:23.602646+00:00 | Debian Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 36.0.0 |
| 2025-04-04T06:25:35.431086+00:00 | Debian Importer | Affected by | VCID-yr2h-w72w-aaab | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-04T03:30:49.772527+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-04T01:22:51.367348+00:00 | Debian Importer | Affected by | VCID-jm31-c3d3-aaap | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-04-04T00:29:48.006733+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 36.0.0 |
| 2025-04-04T00:03:53.919910+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 36.0.0 |
| 2025-04-03T23:45:01.684895+00:00 | Debian Importer | Affected by | VCID-44qv-nzwp-b7ed | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-02-22T06:31:15.805548+00:00 | Debian Importer | Affected by | VCID-z5js-c6pd-yybd | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-22T05:43:51.550759+00:00 | Debian Importer | Affected by | VCID-2bxp-9qmt-aaar | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-22T04:16:37.756870+00:00 | Debian Importer | Affected by | VCID-6uk8-2jnu-aaam | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-21T18:44:52.418036+00:00 | Debian Importer | Affected by | VCID-yr2h-w72w-aaab | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-21T17:55:51.426118+00:00 | Debian Importer | Affected by | VCID-jm31-c3d3-aaap | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-21T17:07:04.742926+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2025-02-21T17:07:04.018407+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | None | 35.1.0 |
| 2025-02-21T12:33:43.167361+00:00 | Debian Importer | Fixing | VCID-2rtj-nbth-aaam | None | 35.1.0 |
| 2025-02-21T12:00:46.648044+00:00 | Debian Importer | Fixing | VCID-5kqm-99x8-aaak | None | 35.1.0 |
| 2025-02-21T10:06:56.800532+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 35.1.0 |
| 2025-02-21T06:57:43.543584+00:00 | Debian Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 35.1.0 |
| 2025-02-21T06:57:40.811574+00:00 | Debian Importer | Fixing | VCID-mu8w-emsy-aaak | None | 35.1.0 |
| 2025-02-21T06:57:37.484216+00:00 | Debian Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 35.1.0 |
| 2025-02-21T06:52:09.265224+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 35.1.0 |
| 2025-02-21T06:50:41.523296+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 35.1.0 |
| 2025-02-21T04:26:41.150698+00:00 | Debian Importer | Fixing | VCID-ec3y-aejm-aaad | None | 35.1.0 |
| 2025-02-21T04:09:22.117346+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 35.1.0 |
| 2025-02-20T16:37:09.069742+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 35.1.0 |
| 2024-12-15T19:03:28.854858+00:00 | Debian Importer | Affected by | VCID-2bxp-9qmt-aaar | https://security-tracker.debian.org/tracker/data/json | 35.0.0 |
| 2024-11-24T13:42:36.798816+00:00 | Debian Importer | Affected by | VCID-6uk8-2jnu-aaam | https://security-tracker.debian.org/tracker/data/json | 35.0.0 |
| 2024-11-24T07:10:45.075599+00:00 | Debian Importer | Affected by | VCID-yr2h-w72w-aaab | https://security-tracker.debian.org/tracker/data/json | 35.0.0 |
| 2024-11-24T06:32:44.644548+00:00 | Debian Importer | Affected by | VCID-jm31-c3d3-aaap | https://security-tracker.debian.org/tracker/data/json | 35.0.0 |
| 2024-11-24T05:47:30.071241+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | https://security-tracker.debian.org/tracker/data/json | 35.0.0 |
| 2024-11-24T01:55:53.274078+00:00 | Debian Importer | Fixing | VCID-2rtj-nbth-aaam | None | 35.0.0 |
| 2024-11-23T23:45:36.885107+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 35.0.0 |
| 2024-11-23T20:45:08.032572+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 35.0.0 |
| 2024-11-23T20:43:33.451340+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 35.0.0 |
| 2024-11-23T18:43:50.943272+00:00 | Debian Importer | Fixing | VCID-ec3y-aejm-aaad | None | 35.0.0 |
| 2024-11-23T18:34:05.285007+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 35.0.0 |
| 2024-11-23T09:32:20.008251+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 35.0.0 |
| 2024-10-20T10:34:30.491436+00:00 | Debian Importer | Affected by | VCID-6uk8-2jnu-aaam | https://security-tracker.debian.org/tracker/data/json | 34.0.2 |
| 2024-10-11T03:51:13.724339+00:00 | Debian Importer | Affected by | VCID-yr2h-w72w-aaab | https://security-tracker.debian.org/tracker/data/json | 34.0.2 |
| 2024-10-11T03:20:04.885918+00:00 | Debian Importer | Affected by | VCID-jm31-c3d3-aaap | https://security-tracker.debian.org/tracker/data/json | 34.0.2 |
| 2024-10-11T02:47:03.879132+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | https://security-tracker.debian.org/tracker/data/json | 34.0.2 |
| 2024-10-10T23:29:14.868244+00:00 | Debian Importer | Fixing | VCID-2rtj-nbth-aaam | None | 34.0.2 |
| 2024-10-10T21:20:59.567793+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 34.0.2 |
| 2024-10-10T18:27:23.994837+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 34.0.2 |
| 2024-10-10T18:26:04.586436+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 34.0.2 |
| 2024-10-10T16:44:37.211850+00:00 | Debian Importer | Fixing | VCID-ec3y-aejm-aaad | None | 34.0.2 |
| 2024-10-10T16:27:20.486066+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 34.0.2 |
| 2024-10-10T07:46:05.873193+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 34.0.2 |
| 2024-09-25T22:12:45.901698+00:00 | Debian Importer | Affected by | VCID-6uk8-2jnu-aaam | https://security-tracker.debian.org/tracker/data/json | 34.0.1 |
| 2024-09-25T18:03:23.397365+00:00 | Debian Importer | Affected by | VCID-yr2h-w72w-aaab | https://security-tracker.debian.org/tracker/data/json | 34.0.1 |
| 2024-09-20T07:31:52.136882+00:00 | Debian Importer | Affected by | VCID-jm31-c3d3-aaap | https://security-tracker.debian.org/tracker/data/json | 34.0.1 |
| 2024-09-20T07:02:23.064286+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | https://security-tracker.debian.org/tracker/data/json | 34.0.1 |
| 2024-09-20T04:13:44.263386+00:00 | Debian Importer | Fixing | VCID-2rtj-nbth-aaam | None | 34.0.1 |
| 2024-09-20T02:21:32.841170+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 34.0.1 |
| 2024-09-19T23:46:01.699420+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 34.0.1 |
| 2024-09-19T23:44:45.096371+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 34.0.1 |
| 2024-09-19T22:20:05.452346+00:00 | Debian Importer | Fixing | VCID-ec3y-aejm-aaad | None | 34.0.1 |
| 2024-09-19T22:10:54.680988+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 34.0.1 |
| 2024-09-19T14:20:13.254032+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 34.0.1 |
| 2024-05-20T15:56:32.473002+00:00 | Debian Importer | Affected by | VCID-jm31-c3d3-aaap | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc4 |
| 2024-05-20T15:35:22.812189+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc4 |
| 2024-05-20T15:35:21.848183+00:00 | Debian Importer | Affected by | VCID-kc39-vfd3-aaad | None | 34.0.0rc4 |
| 2024-04-26T04:11:18.943670+00:00 | Debian Importer | Fixing | VCID-2rtj-nbth-aaam | None | 34.0.0rc4 |
| 2024-04-26T03:37:53.555472+00:00 | Debian Importer | Fixing | VCID-5kqm-99x8-aaak | None | 34.0.0rc4 |
| 2024-04-26T02:17:19.799403+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 34.0.0rc4 |
| 2024-04-25T23:34:03.877251+00:00 | Debian Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 34.0.0rc4 |
| 2024-04-25T23:34:01.393897+00:00 | Debian Importer | Fixing | VCID-mu8w-emsy-aaak | None | 34.0.0rc4 |
| 2024-04-25T23:33:01.808156+00:00 | Debian Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 34.0.0rc4 |
| 2024-04-25T23:28:14.005490+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 34.0.0rc4 |
| 2024-04-25T23:26:29.146040+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 34.0.0rc4 |
| 2024-04-25T21:37:04.275476+00:00 | Debian Importer | Fixing | VCID-ec3y-aejm-aaad | None | 34.0.0rc4 |
| 2024-04-25T21:23:35.357109+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 34.0.0rc4 |
| 2024-04-25T11:35:14.207338+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 34.0.0rc4 |
| 2024-01-12T13:44:31.415289+00:00 | Debian Importer | Fixing | VCID-2rtj-nbth-aaam | None | 34.0.0rc2 |
| 2024-01-12T13:24:54.693075+00:00 | Debian Importer | Fixing | VCID-5kqm-99x8-aaak | None | 34.0.0rc2 |
| 2024-01-12T12:14:51.283820+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 34.0.0rc2 |
| 2024-01-12T08:47:55.401066+00:00 | Debian Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 34.0.0rc2 |
| 2024-01-12T08:47:50.075352+00:00 | Debian Importer | Fixing | VCID-mu8w-emsy-aaak | None | 34.0.0rc2 |
| 2024-01-12T08:47:43.441690+00:00 | Debian Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 34.0.0rc2 |
| 2024-01-12T08:43:05.731130+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 34.0.0rc2 |
| 2024-01-12T08:42:14.642320+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 34.0.0rc2 |
| 2024-01-12T07:38:51.794464+00:00 | Debian Importer | Fixing | VCID-ec3y-aejm-aaad | None | 34.0.0rc2 |
| 2024-01-12T07:05:01.106819+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 34.0.0rc2 |
| 2024-01-11T13:31:01.451498+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 34.0.0rc2 |
| 2024-01-05T09:18:26.140859+00:00 | Debian Importer | Fixing | VCID-2rtj-nbth-aaam | None | 34.0.0rc1 |
| 2024-01-05T09:03:04.919087+00:00 | Debian Importer | Fixing | VCID-5kqm-99x8-aaak | None | 34.0.0rc1 |
| 2024-01-05T08:14:13.486436+00:00 | Debian Importer | Fixing | VCID-xda1-h5nv-aaaf | None | 34.0.0rc1 |
| 2024-01-05T06:34:26.785424+00:00 | Debian Importer | Fixing | VCID-kn8m-m9v4-aaaa | None | 34.0.0rc1 |
| 2024-01-05T06:34:24.535689+00:00 | Debian Importer | Fixing | VCID-mu8w-emsy-aaak | None | 34.0.0rc1 |
| 2024-01-05T06:34:22.180475+00:00 | Debian Importer | Fixing | VCID-tkv7-cnhy-aaas | None | 34.0.0rc1 |
| 2024-01-05T06:30:51.973849+00:00 | Debian Importer | Fixing | VCID-9wtx-9sbn-aaam | None | 34.0.0rc1 |
| 2024-01-05T06:30:06.029171+00:00 | Debian Importer | Fixing | VCID-uua4-ygek-aaah | None | 34.0.0rc1 |
| 2024-01-05T05:46:00.845530+00:00 | Debian Importer | Fixing | VCID-ec3y-aejm-aaad | None | 34.0.0rc1 |
| 2024-01-05T05:35:29.791222+00:00 | Debian Importer | Fixing | VCID-ur7f-5ey8-aaak | None | 34.0.0rc1 |
| 2024-01-04T23:09:26.172061+00:00 | Debian Importer | Fixing | VCID-5khv-27u8-aaaa | None | 34.0.0rc1 |