Show filters
1,184 Total Results
Displaying 51-60 of 1,184
Sort by:
Attacker Value
Unknown

CVE-2022-1927

Disclosure Date: May 29, 2022 (last updated November 08, 2023)
Buffer Over-read in GitHub repository vim/vim prior to 8.2.
Attacker Value
Unknown

CVE-2022-1897

Disclosure Date: May 27, 2022 (last updated November 08, 2023)
Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
Attacker Value
Unknown

CVE-2022-1898

Disclosure Date: May 27, 2022 (last updated November 08, 2023)
Use After Free in GitHub repository vim/vim prior to 8.2.
Attacker Value
Unknown

CVE-2022-1851

Disclosure Date: May 25, 2022 (last updated November 08, 2023)
Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
Attacker Value
Unknown

CVE-2022-30600

Disclosure Date: May 18, 2022 (last updated October 07, 2023)
A flaw was found in moodle where logic used to count failed login attempts could result in the account lockout threshold being bypassed.
Attacker Value
Unknown

CVE-2022-30599

Disclosure Date: May 18, 2022 (last updated October 07, 2023)
A flaw was found in moodle where an SQL injection risk was identified in Badges code relating to configuring criteria.
Attacker Value
Unknown

CVE-2022-30598

Disclosure Date: May 18, 2022 (last updated October 07, 2023)
A flaw was found in moodle where global search results could include author information on some activities where a user may not otherwise have access to it.
Attacker Value
Unknown

CVE-2022-30597

Disclosure Date: May 18, 2022 (last updated October 07, 2023)
A flaw was found in moodle where the description user field was not hidden when being set as a hidden user field.
Attacker Value
Unknown

CVE-2022-30596

Disclosure Date: May 18, 2022 (last updated October 07, 2023)
A flaw was found in moodle where ID numbers displayed when bulk allocating markers to assignments required additional sanitizing to prevent a stored XSS risk.
Attacker Value
Unknown

CVE-2022-29162

Disclosure Date: May 17, 2022 (last updated October 07, 2023)
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes `runc exec --cap` behavior such that the additional capabilities granted to the process being executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`) file.