Approved changes feed: RSS · Atom

cpe:2.3:o:netapp:h610c_firmware:-:*:*:*:*:*:*:*

part: o version: - update: *

VendorNetapp (f19678f6-cb27-5a55-8852-34b249f80ef9)
ProductH610C Firmware (917b7fee-2d69-5c91-8d23-d29d46b7adaa)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-0167 vulnerable 2026-06-08 07:00:29.838458 netrc and default credential leak
When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has a `default` entry that omits both login and password. A rare circumstance.
Published: 2025-02-05T09:15:06.891Z
Updated: 2025-03-07T00:10:48.290Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-6119 vulnerable 2026-06-08 06:58:17.853068 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-33601 vulnerable 2026-06-08 06:37:31.763148 nscd: netgroup cache may terminate daemon on memory allocation failure
nscd: netgroup cache may terminate daemon on memory allocation failure The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
Published: 2024-05-06T19:22:07.763Z
Updated: 2026-07-14T12:37:52.755Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-33600 vulnerable 2026-06-08 06:37:31.754885 nscd: Null pointer crashes after notfound response
nscd: Null pointer crashes after notfound response If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
Published: 2024-05-06T19:22:02.726Z
Updated: 2026-07-14T12:37:51.545Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-2398 vulnerable 2026-06-08 06:33:31.017893 HTTP/2 push headers memory-leak
When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.
Published: 2024-03-27T07:55:48.524Z
Updated: 2025-02-13T17:40:07.893Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-2379 vulnerable 2026-06-08 06:33:30.968317 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-28757 vulnerable 2026-06-08 06:33:27.226660 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-26735 vulnerable 2026-06-08 06:31:26.805852 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-26733 vulnerable 2026-06-08 06:31:26.800812 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-26633 vulnerable 2026-06-08 06:31:26.601246 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-26462 vulnerable 2026-06-08 06:31:26.413570 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-26461 vulnerable 2026-06-08 06:31:26.412247 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-26458 vulnerable 2026-06-08 06:31:26.406217 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-11053 vulnerable 2026-06-08 06:23:48.606610 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-52585 vulnerable 2026-06-08 06:17:55.381971 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-36879 vulnerable 2026-06-08 05:46:07.956779 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-2068 vulnerable 2026-06-08 05:42:50.197747 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-0995 vulnerable 2026-06-08 05:39:11.626348 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-45485 vulnerable 2026-06-08 05:36:48.239608 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-40490 vulnerable 2026-06-08 05:35:18.458489 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-3772 vulnerable 2026-06-08 05:33:53.983636 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-3609 vulnerable 2026-06-08 05:33:53.111970 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-36086 vulnerable 2026-06-08 05:32:49.700685 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-22555 vulnerable 2026-06-08 05:30:00.863379 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-8835 vulnerable 2026-06-08 05:27:19.804304 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-8832 vulnerable 2026-06-08 05:27:19.765562 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-36516 vulnerable 2026-06-08 05:25:49.001943 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-35508 vulnerable 2026-06-08 05:25:01.248185 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-15436 vulnerable 2026-06-08 05:19:25.923639 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-13143 vulnerable 2026-06-08 05:18:00.226960 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-12888 vulnerable 2026-06-08 05:17:59.534799 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-12771 vulnerable 2026-06-08 05:17:59.093818 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-12770 vulnerable 2026-06-08 05:17:59.067438 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-12769 vulnerable 2026-06-08 05:17:59.063674 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-12653 vulnerable 2026-06-08 05:17:58.689998 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-11884 vulnerable 2026-06-08 05:17:55.184762 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-10690 vulnerable 2026-06-08 05:16:35.659493 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-25045 vulnerable 2026-06-08 05:13:41.868218 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.