NetApp 500f Firmware -
Approved changes feed: RSS · Atom
cpe:2.3:o:netapp:500f_firmware:-:*:*:*:*:*:*:*
part: o version: - update: *
| Vendor | Netapp (f19678f6-cb27-5a55-8852-34b249f80ef9) |
|---|---|
| Product | 500F Firmware (a2f08ded-3d97-5454-8fe5-b7cf0b78e53c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-6387 |
vulnerable | 2026-06-08 06:58:19.284285 |
Openssh: regresshion - race condition in ssh allows rce/dos
HIGH (8.1)
A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period.
Published: 2024-07-01T12:37:25.431Z
Updated: 2026-07-14T12:37:29.376Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6119 |
vulnerable | 2026-06-08 06:58:17.862942 |
Possible denial of service in X.509 name checks
Issue summary: Applications performing certificate name checks (e.g., TLS
clients checking server certificates) may attempt to read an invalid memory
address resulting in abnormal termination of the application process.
Impact summary: Abnormal termination of an application can a cause a denial of
service.
Applications performing certificate name checks (e.g., TLS clients checking
server certificates) may attempt to read an invalid memory address when
comparing the expected name with an `otherName` subject alternative name of an
X.509 certificate. This may result in an exception that terminates the
application program.
Note that basic certificate chain validation (signatures, dates, ...) is not
affected, the denial of service can occur only when the application also
specifies an expected DNS name, Email address or IP address.
TLS servers rarely solicit client certificates, and even when they do, they
generally don't perform a name check against a reference identifier (expected
identity), but rather extract the presented identity after checking the
certificate chain. So TLS servers are generally not affected and the severity
of the issue is Moderate.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Published: 2024-09-03T15:58:06.970Z
Updated: 2026-07-14T12:37:27.827Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1086 |
vulnerable | 2026-06-08 06:25:39.220744 |
Use-after-free in Linux kernel's netfilter: nf_tables component
HIGH (7.8)
A use-after-free vulnerability in the Linux kernel's netfilter: nf_tables component can be exploited to achieve local privilege escalation.
The nft_verdict_init() function allows positive values as drop error within the hook verdict, and hence the nf_hook_slow() function can cause a double free vulnerability when NF_DROP is issued with a drop error which resembles NF_ACCEPT.
We recommend upgrading past commit f342de4e2f33e0e39165d8639387aa6c19dff660.
Published: 2024-01-31T12:14:34.073Z
Updated: 2025-10-21T23:05:25.720Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-25136 |
vulnerable | 2026-06-08 05:56:08.560254 |
Details available
OpenSSH server (sshd) 9.1 introduced a double-free vulnerability during options.kex_algorithms handling. This is fixed in OpenSSH 9.2. The double free can be leveraged, by an unauthenticated remote attacker in the default configuration, to jump to any location in the sshd address space. One third-party report states "remote code execution is theoretically possible."
Published: 2023-02-03T00:00:00.000Z
Updated: 2026-05-28T17:43:14.037Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-0778 |
vulnerable | 2026-06-08 05:39:11.190120 |
Infinite loop in BN_mod_sqrt() reachable when parsing certificates
The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).
Published: 2022-03-15T17:05:20.382Z
Updated: 2026-05-22T13:28:08.544Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-4044 |
vulnerable | 2026-06-08 05:38:08.208328 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-31879 |
vulnerable | 2026-06-08 05:31:54.072416 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-25215 |
vulnerable | 2026-06-08 05:30:40.275360 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-8625 |
vulnerable | 2026-06-08 05:27:17.093088 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-29374 |
vulnerable | 2026-06-08 05:24:58.159886 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-27618 |
vulnerable | 2026-06-08 05:23:52.828850 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-25668 |
vulnerable | 2026-06-08 05:22:37.148817 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-25013 |
vulnerable | 2026-06-08 05:13:41.803145 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.