NetApp Brocade Fabric Operating System
Approved changes feed: RSS · Atom
cpe:2.3:o:netapp:brocade_fabric_operating_system:-:*:*:*:*:*:*:*
part: o version: - update: *
| Vendor | Netapp (f19678f6-cb27-5a55-8852-34b249f80ef9) |
|---|---|
| Product | Brocade Fabric Operating System (811269ba-547a-5d94-8aae-ceed817be850) |
| 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-6119 |
vulnerable | 2026-06-08 06:58:17.842949 |
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-2398 |
vulnerable | 2026-06-08 06:33:31.017446 |
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-2023-28531 |
vulnerable | 2026-06-08 06:01:11.063703 |
Details available
ssh-add in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination constraints. The earliest affected version is 8.9.
Published: 2023-03-17T00:00:00.000Z
Updated: 2026-07-14T12:03:12.080Z Reference links
|
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.