Page 11 of 10600 results (0.038 seconds)

CVSS: 5.0EPSS: 0%CPEs: 4EXPL: 0

This could lead to local information disclosure with User execution privileges needed. • https://android.googlesource.com/platform/frameworks/base/+/4677d3ee0ec2d31acc6108fea7be6cced971da37 https://source.android.com/security/bulletin/2024-11-01 • CWE-862: Missing Authorization •

CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0

This could lead to local information disclosure with no additional execution privileges needed. • https://android.googlesource.com/platform/frameworks/base/+/55a3d36701bb874358f685d3ac3381eda10fcff0 https://source.android.com/security/bulletin/2024-11-01 • CWE-276: Incorrect Default Permissions •

CVSS: 6.2EPSS: 0%CPEs: 5EXPL: 0

In visitUris of multiple files, there is a possible information disclosure due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. • https://android.googlesource.com/platform/frameworks/base/+/50eec20b570cd4cbbe8c5971af4c9dda3ddcb858 https://source.android.com/security/bulletin/2024-11-01 •

CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0

This could lead to local information disclosure with no additional execution privileges needed. • https://android.googlesource.com/platform/frameworks/base/+/6aa1b4fbf5936a1ff5bdbb79397c94910a6ed8f5 https://source.android.com/security/bulletin/2024-11-01 • CWE-125: Out-of-bounds Read •

CVSS: 5.7EPSS: 0%CPEs: 2EXPL: 0

An information disclosure vulnerability exists in the backup configuration process where the SAS token is not masked in the configuration response. This oversight results in sensitive information leakage within the yb_backup log files, exposing the SAS token in plaintext. The leakage occurs during the backup procedure, leading to potential unauthorized access to resources associated with the SAS token.  • https://github.com/yugabyte/yugabyte-db/commit/920989b6c0db0222bb7a0cce46febc76cf72d438 • CWE-532: Insertion of Sensitive Information into Log File •