CVE Intelligence
Skip to main content
MEDIUM

CVE-2025-12774

CVE-2025-12774 — SQL queries with sensitive information printed in logs with Brocade SANnav before 3.0

A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries in the SANnav support save file. An attacker with access to Brocade SANnav supportsave file, could open the file and then obtain sensitive information such as details of database tables and encrypted passwords.

Published Updated Sources: cvelistV5, brocade

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

brocade

sannav

CVSS base

4.6

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

brocade

Products (1)

sannav

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
4.6CVSS 4.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-312

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1005Data from Local System
  • T1552.004Unsecured Credentials: Private Keys

References

1 on the record

Elsewhere on this site

  • brocadeevery CVE for this vendor
  • CWE-312other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.