[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fx5dThE1Nrb26_NnXY_V0DD7hqI6l4stMwAoMF8KIFnY":3,"g5a-ex:broadcom\u002Fbrocade_sannav@*":148,"g5a-family:broadcom\u002Fbrocade_sannav":150},{"success":4,"data":5},true,{"product":6,"versions":49,"topVulnerabilitiesByEpss":66,"kevVulnerabilities":125,"seoMetadata":126,"meta":145},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":48},"broadcom","brocade_sannav",16,54,0,"2025-07-10",[14,17,19,21,23,25,27,29,31,33,35,37,40,42,44,46],{"version":15,"cve_count":11,"kev_count":11,"has_kev":16},"1.1.0",false,{"version":18,"cve_count":11,"kev_count":11,"has_kev":16},"1.1.1",{"version":20,"cve_count":11,"kev_count":11,"has_kev":16},"2.0",{"version":22,"cve_count":11,"kev_count":11,"has_kev":16},"2.1.0",{"version":24,"cve_count":11,"kev_count":11,"has_kev":16},"2.1.1",{"version":26,"cve_count":11,"kev_count":11,"has_kev":16},"2.2.0",{"version":28,"cve_count":11,"kev_count":11,"has_kev":16},"2.2.1",{"version":30,"cve_count":11,"kev_count":11,"has_kev":16},"2.2.2",{"version":32,"cve_count":11,"kev_count":11,"has_kev":16},"2.2.2a",{"version":34,"cve_count":11,"kev_count":11,"has_kev":16},"2.3.0",{"version":36,"cve_count":11,"kev_count":11,"has_kev":16},"2.3.0a",{"version":38,"cve_count":39,"kev_count":11,"has_kev":16},"2.3.1",1,{"version":41,"cve_count":11,"kev_count":11,"has_kev":16},"2.3.1a",{"version":43,"cve_count":11,"kev_count":11,"has_kev":16},"2.3.1b",{"version":45,"cve_count":11,"kev_count":11,"has_kev":16},"2.4.0",{"version":47,"cve_count":11,"kev_count":11,"has_kev":16},"2.4.0a","Brocade Sannav by Broadcom is a technology product with 16 tracked versions and 54 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65],{"version":15,"cve_count":11,"kev_count":11,"has_kev":16},{"version":18,"cve_count":11,"kev_count":11,"has_kev":16},{"version":20,"cve_count":11,"kev_count":11,"has_kev":16},{"version":22,"cve_count":11,"kev_count":11,"has_kev":16},{"version":24,"cve_count":11,"kev_count":11,"has_kev":16},{"version":26,"cve_count":11,"kev_count":11,"has_kev":16},{"version":28,"cve_count":11,"kev_count":11,"has_kev":16},{"version":30,"cve_count":11,"kev_count":11,"has_kev":16},{"version":32,"cve_count":11,"kev_count":11,"has_kev":16},{"version":34,"cve_count":11,"kev_count":11,"has_kev":16},{"version":36,"cve_count":11,"kev_count":11,"has_kev":16},{"version":38,"cve_count":39,"kev_count":11,"has_kev":16},{"version":41,"cve_count":11,"kev_count":11,"has_kev":16},{"version":43,"cve_count":11,"kev_count":11,"has_kev":16},{"version":45,"cve_count":11,"kev_count":11,"has_kev":16},{"version":47,"cve_count":11,"kev_count":11,"has_kev":16},[67,75,81,87,92,97,103,107,113,118],{"cveId":68,"description":69,"publishedDate":70,"cvssScore":71,"cvssVersion":72,"severity":73,"isKev":16,"epssScore":74},"CVE-2022-23305","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.","2022-01-18",9.8,"v3.1","Critical",0.66537,{"cveId":76,"description":77,"publishedDate":70,"cvssScore":78,"cvssVersion":72,"severity":79,"isKev":16,"epssScore":80},"CVE-2022-23302","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.",8.8,"High",0.63841,{"cveId":82,"description":83,"publishedDate":84,"cvssScore":85,"cvssVersion":72,"severity":73,"isKev":16,"epssScore":86},"CVE-2024-3596","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.","2024-07-09",9,0.14859,{"cveId":88,"description":89,"publishedDate":90,"cvssScore":78,"cvssVersion":72,"severity":79,"isKev":16,"epssScore":91},"CVE-2019-16212","A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection. The vulnerability could allow a remote attacker to bypass the authentication process.","2020-09-25",0.01865,{"cveId":93,"description":94,"publishedDate":95,"cvssScore":78,"cvssVersion":72,"severity":79,"isKev":16,"epssScore":96},"CVE-2019-16205","A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID. The vulnerability is due to an insufficiently random session ID for several post-authentication actions in the SANnav portal.","2019-11-08",0.01293,{"cveId":98,"description":99,"publishedDate":100,"cvssScore":101,"cvssVersion":72,"severity":79,"isKev":16,"epssScore":102},"CVE-2020-15379","Brocade SANnav before v.2.1.0a could allow remote attackers cause a denial-of-service condition due to a lack of proper validation, of the length of user-supplied data as name for custom field name.","2021-06-09",7.5,0.01271,{"cveId":104,"description":105,"publishedDate":90,"cvssScore":71,"cvssVersion":72,"severity":73,"isKev":16,"epssScore":106},"CVE-2019-16211","Brocade SANnav versions before v2.1.0, contain a Plaintext Password Storage vulnerability.",0.01032,{"cveId":108,"description":109,"publishedDate":110,"cvssScore":111,"cvssVersion":72,"severity":79,"isKev":16,"epssScore":112},"CVE-2023-31424","Brocade SANnav Web interface before Brocade SANnav v2.3.0 and v2.2.2a\n allows remote unauthenticated users to bypass web authentication and \nauthorization.","2023-08-31",8.1,0.009,{"cveId":114,"description":115,"publishedDate":100,"cvssScore":116,"cvssVersion":72,"severity":79,"isKev":16,"epssScore":117},"CVE-2020-15382","Brocade SANnav before version 2.1.1 uses a hard-coded administrator account with the weak password ‘passw0rd’ if a password is not provided for PostgreSQL at install-time.",7.2,0.00863,{"cveId":119,"description":120,"publishedDate":121,"cvssScore":122,"cvssVersion":72,"severity":123,"isKev":16,"epssScore":124},"CVE-2024-2859","By default, SANnav OVA is shipped with root user login enabled.  While protected by a password, access to root could expose SANnav to a remote attacker should they gain access to the root account.","2024-04-27",6.8,"Medium",0.00848,[],{"title":127,"metaDescription":128,"keywords":129,"structuredData":130},"Brocade Sannav by Broadcom - Security Vulnerabilities & Analysis | EdgeProtect","Comprehensive security analysis for Brocade Sannav by Broadcom covering 16 versions with 54 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Brocade Sannav vulnerabilities, Brocade Sannav security, Brocade Sannav CVE, Broadcom Brocade Sannav, Brocade Sannav threat intelligence, Broadcom security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":131,"@type":132,"name":133,"description":128,"url":134,"manufacturer":135,"applicationCategory":139,"softwareVersion":140,"mainEntity":141},"https:\u002F\u002Fschema.org","SoftwareApplication","Brocade Sannav","https:\u002F\u002Fedgeprotect.io\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Fbroadcom\u002Fbrocade_sannav",{"@type":136,"name":137,"url":138},"Organization","Broadcom","https:\u002F\u002Fedgeprotect.io\u002Fvendors\u002Fbroadcom","Security Software","16 versions tracked",{"@type":142,"name":143,"description":144,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","Brocade Sannav Security Vulnerabilities","Security vulnerabilities affecting Brocade Sannav by Broadcom",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":146,"apiVersion":147},"2026-10-28T15:25:57.380Z","3.0",{"rows":149,"total":11,"capped":16,"failed":11},[],[]]