CVE-2024-29962: Insecure file permission setting that makes files world-readable
First published: Fri Apr 19 2024(Updated: )
Brocade SANnav OVA before v2.3.1 and v2.3.0a have an insecure file permission setting that makes files world-readable. This could allow a local user without the required privileges to access sensitive information or a Java binary.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom Brocade SANnav | <2.3.1 | |
| Broadcom Brocade SANnav | <2.3.0a | |
| Brocade SANnav | <2.3.0a |
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-29962?
CVE-2024-29962 has been classified as a medium severity vulnerability due to its potential for exposing sensitive information.
How do I fix CVE-2024-29962?
To fix CVE-2024-29962, upgrade Brocade SANnav OVA to version 2.3.1 or 2.3.0a to ensure proper file permissions.
What impact does CVE-2024-29962 have on my system?
CVE-2024-29962 allows local users to access sensitive files and information due to insecure file permissions.
Who is affected by CVE-2024-29962?
CVE-2024-29962 affects users of Brocade SANnav OVA prior to version 2.3.1 and version 2.3.0a.
What are the common mitigation strategies for CVE-2024-29962?
Common mitigation strategies for CVE-2024-29962 include applying the latest updates and ensuring appropriate file permissions are set.
- agent/weakness
- agent/references
- agent/title
- agent/description
- agent/type
- agent/first-publish-date
- agent/severity
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- vendor/brocade
- canonical/broadcom brocade sannav
- vendor/broadcom
- canonical/brocade sannav