NetApp Management Services for Element Software
Approved changes feed: RSS · Atom
cpe:2.3:a:netapp:management_services_for_element_software:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Netapp (f19678f6-cb27-5a55-8852-34b249f80ef9) |
|---|---|
| Product | Management Services For Element Software (870fb7da-f91f-537b-a8a3-a74b374a6afa) |
| 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-2023-37920 |
vulnerable | 2026-06-08 06:08:16.216217 |
Certifi's removal of e-Tugra root certificate
HIGH (7.5)
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi prior to version 2023.07.22 recognizes "e-Tugra" root certificates. e-Tugra's root certificates were subject to an investigation prompted by reporting of security issues in their systems. Certifi 2023.07.22 removes root certificates from "e-Tugra" from the root store.
Published: 2023-07-25T20:45:35.286Z
Updated: 2025-03-05T18:47:15.819Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-36054 |
vulnerable | 2026-06-08 06:06:28.532905 |
Details available
lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.
Published: 2023-08-07T00:00:00.000Z
Updated: 2024-10-11T13:57:10.192Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-24329 |
vulnerable | 2026-06-08 05:56:05.303664 |
Details available
An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.
Published: 2023-02-17T00:00:00.000Z
Updated: 2025-11-03T21:47:22.781Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-45061 |
vulnerable | 2026-06-08 05:50:35.537088 |
Details available
An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.
Published: 2022-11-09T00:00:00.000Z
Updated: 2025-11-03T21:46:44.155Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-3996 |
vulnerable | 2026-06-08 05:48:22.791258 |
X.509 Policy Constraints Double Locking
If an X.509 certificate contains a malformed policy constraint and
policy processing is enabled, then a write lock will be taken twice
recursively. On some operating systems (most widely: Windows) this
results in a denial of service when the affected process hangs. Policy
processing being enabled on a publicly facing server is not considered
to be a common setup.
Policy processing is enabled by passing the `-policy'
argument to the command line utilities or by calling the
`X509_VERIFY_PARAM_set1_policies()' function.
Update (31 March 2023): The description of the policy processing enablement
was corrected based on CVE-2023-0466.
Published: 2022-12-13T15:43:06.821Z
Updated: 2024-08-03T01:27:54.475Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-38023 |
vulnerable | 2026-06-08 05:47:14.150716 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-37967 |
vulnerable | 2026-06-08 05:47:13.584182 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-37966 |
vulnerable | 2026-06-08 05:47:13.578002 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-37434 |
vulnerable | 2026-06-08 05:47:12.874113 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-36033 |
vulnerable | 2026-06-08 05:46:06.195820 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24736 |
vulnerable | 2026-06-08 05:41:01.487025 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24735 |
vulnerable | 2026-06-08 05:41:01.481272 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23491 |
vulnerable | 2026-06-08 05:40:57.634665 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-0391 |
vulnerable | 2026-06-08 05:39:09.948678 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-42340 |
vulnerable | 2026-06-08 05:35:22.180997 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3737 |
vulnerable | 2026-06-08 05:33:53.879293 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3671 |
vulnerable | 2026-06-08 05:33:53.381395 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32762 |
vulnerable | 2026-06-08 05:32:07.984592 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32687 |
vulnerable | 2026-06-08 05:32:07.839827 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32675 |
vulnerable | 2026-06-08 05:32:07.814066 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32672 |
vulnerable | 2026-06-08 05:32:07.808781 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32628 |
vulnerable | 2026-06-08 05:32:07.700434 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32627 |
vulnerable | 2026-06-08 05:32:07.699544 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32626 |
vulnerable | 2026-06-08 05:32:07.693927 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-28169 |
vulnerable | 2026-06-08 05:31:23.114515 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-22118 |
vulnerable | 2026-06-08 05:29:59.867097 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-27223 |
vulnerable | 2026-06-08 05:23:52.427540 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-25032 |
vulnerable | 2026-06-08 05:11:29.194196 | 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.