CVE-2024-4161: Syslog traffic sent in clear-text
First published: Thu Apr 25 2024(Updated: )
In Brocade SANnav, before Brocade SANnav v2.3.0, syslog traffic received clear text. This could allow an unauthenticated, remote attacker to capture sensitive information.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom SANnav OVA | <2.3.0 | |
| Broadcom SANnav OVA | <2.3.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2024-4161?
CVE-2024-4161 is considered a high severity vulnerability due to its potential for unauthorized data capture.
How do I fix CVE-2024-4161?
To fix CVE-2024-4161, upgrade Brocade SANnav to version 2.3.0 or later.
What type of data is exposed in CVE-2024-4161?
CVE-2024-4161 exposes sensitive information transmitted via clear text syslog traffic.
Who is affected by CVE-2024-4161?
Organizations using Brocade SANnav versions prior to 2.3.0 are affected by CVE-2024-4161.
Can CVE-2024-4161 be exploited remotely?
Yes, CVE-2024-4161 can be exploited remotely by an unauthenticated attacker.
- agent/references
- agent/weakness
- agent/title
- agent/description
- agent/first-publish-date
- agent/type
- agent/author
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/last-modified-date
- agent/severity
- agent/event
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- vendor/brocade
- canonical/broadcom sannav ova
- vendor/broadcom