| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| PDFL SDK versions 21.0.0.5 and earlier are affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file. |
| In fm_set_stat of mediatek FM radio driver, there is a possible OOB write
due to improper input validation. This could lead to local escalation of
privilege with System execution privileges needed. User interaction is not
needed for exploitation. |
| In /proc/driver/wmt_dbg driver, there are several possible out of bounds
writes. These could lead to local escalation of privilege with System
execution privileges needed. User interaction is not needed for
exploitation. |
| In store_cmd of ftm4_pdc.c, there is a possible out of bounds write due to
an incorrect bounds check. This could lead to local escalation of privilege
with System execution privileges needed. User interaction is not needed for
exploitation. |
| In sw49408_irq_runtime_engine_debug of touch_sw49408.c, there is a possible
out of bounds write due to an incorrect bounds check. This could lead to
local escalation of privilege with System execution privileges needed. User
interaction is not needed for exploitation. |
| The conformance validation endpoint is public so everybody can verify the conformance of onboarded services. The response could contain specific information about the service, including available endpoints, and swagger. It could advise about the running version of a service to an attacker. The attacker could also check if a service is running. |
| The health endpoint is public so everybody can see a list of all services. It is potentially valuable information for attackers. |
| In tscpu_write_GPIO_out and mtkts_Abts_write of mtk_ts_Abts.c, there is a possible buffer overflow in an sscanf due to improper input validation. This could lead to a local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. |
| In reboot_block_command of htc reboot_block driver, there is a possible
stack buffer overflow due to a missing bounds check. This could lead to
local escalation of privilege with System execution privileges needed. User
interaction is not needed for exploitation. |
| In store_upgrade and store_cmd of drivers/input/touchscreen/stm/ftm4_pdc.c, there are out of bound writes due to missing bounds checks or integer underflows. These could lead to escalation of privilege. |
| In procfile_write of gl_proc.c, there is a possible out of bounds read of a
function pointer due to an incorrect bounds check. This could lead to local
escalation of privilege with System execution privileges needed. User
interaction is not needed for exploitation. |
| In gt1x_debug_write_proc and gt1x_tool_write of
drivers/input/touchscreen/mediatek/GT1151/gt1x_generic.c and gt1x_tools.c,
there is a possible out of bounds write due to a missing bounds check. This
could lead to local escalation of privilege with System execution privileges
needed. User interaction is not needed for exploitation. |
| In multiple functions of gl_proc.c, there is a buffer overwrite due to a missing bounds check. This could lead to escalation of privileges in the kernel. |
| In the MTK_FLP_MSG_HAL_DIAG_REPORT_DATA_NTF handler of flp2hal_-
interface.c, there is a possible stack buffer overflow due to a missing
bounds check. This could lead to local escalation of privilege in a
privileged process with System execution privileges needed. User interaction
is not needed for exploitation. |
| In oemCallback of ril.cpp, there is a possible out of bounds write due to an
integer overflow. This could lead to local escalation of privilege with
System execution privileges needed. User interaction is not needed for
exploitation. |
| In emmc_rpmb_ioctl of emmc_rpmb.c, there is an Information Disclosure due to a Missing Bounds Check. This could lead to Information Disclosure of kernel data. |
| In m3326_gps_write and m3326_gps_read of gps.s, there is a possible Out Of
Bounds Read due to a missing bounds check. This could lead to a local
information disclosure with System execution privileges needed. User
interaction is not needed for exploitation. |
| In __unregister_prot_hook and packet_release of af_packet.c, there is a
possible use-after-free due to improper locking. This could lead to local
escalation of privilege in the kernel with System execution privileges
needed. User interaction is not needed for exploitation. |
| This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Starting in version 1.14.0 and prior to versions 1.14.16 and 1.15.10, a policy rule denying a prefix that is broader than `/32` may be ignored if there is a policy rule referencing a more narrow prefix (`CIDRSet` or `toFQDN`) and this narrower policy rule specifies either `enableDefaultDeny: false` or `- toEntities: all`. Note that a rule specifying `toEntities: world` or `toEntities: 0.0.0.0/0` is insufficient, it must be to entity `all`.This issue has been patched in Cilium v1.14.16 and v1.15.10. As this issue only affects policies using `enableDefaultDeny: false` or that set `toEntities` to `all`, some workarounds are available. For users with policies using `enableDefaultDeny: false`, remove this configuration option and explicitly define any allow rules required. For users with egress policies that explicitly specify `toEntities: all`, use `toEntities: world`. |
