Broadcom Brocade SAN Navigator (SANnav)
Approved changes feed: RSS · Atom
cpe:2.3:a:broadcom:brocade_sannav:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Broadcom (9814e701-1071-5d68-93ef-4536eaf59407) |
|---|---|
| Product | Brocade Sannav (b39d65d0-a4c9-557f-af8a-e743bfb195ee) |
| 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-3596 |
vulnerable | 2026-06-08 06:43:50.929187 |
RADIUS Protocol under RFC2865 is vulnerable to forgery attacks.
RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.
Published: 2024-07-09T12:02:53.001Z
Updated: 2026-06-09T09:01:52.617Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23305 |
vulnerable | 2026-06-08 05:40:56.944591 |
SQL injection in JDBC Appender in Apache Log4j V1
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Published: 2022-01-18T15:25:22.000Z
Updated: 2026-05-27T13:40:57.853Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23302 |
vulnerable | 2026-06-08 05:40:56.909003 |
Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Published: 2022-01-18T15:25:20.000Z
Updated: 2026-05-27T13:46:05.384Z |
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.