CVE-2022-3411
published 2023-02-13CVE-2022-3411: A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authenticated…
PriorityP433medium6.5CVSS 3.1
AVNACLPRLUINSUCNINAH
EPSS
1.25%
69.1th percentile
A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | gitlab | < gitlab 15.10.8+ds1-2 (sid) | gitlab 15.10.8+ds1-2 (sid) |
| gitlab | gitlab | — | — |
| gitlab | gitlab | — | — |
| gitlab | gitlab | — | — |
| gitlab | gitlab | — | — |
| gitlab | gitlab | >= 12.4 < 15.6.7 | 15.6.7 |
| gitlab | gitlab | >= 15.7 < 15.7.6 | 15.7.6 |
| gitlab | gitlab | >= 15.8 < 15.8.1 | 15.8.1 |
| gitlab | gitlab_ce | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv6.5MEDIUM
vendor_debian6.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: gpiolib: fix memory leak in gpiochip_setup_dev()
vendor_redhat·2024-10-21·CVSS 5.5
CVE-2022-48975 [MEDIUM] CWE-401 kernel: gpiolib: fix memory leak in gpiochip_setup_dev()
kernel: gpiolib: fix memory leak in gpiochip_setup_dev()
In the Linux kernel, the following vulnerability has been resolved:
gpiolib: fix memory leak in gpiochip_setup_dev()
Here is a backtrace report about memory leak detected in
gpiochip_setup_dev():
unreferenced object 0xffff88810b406400 (size 512):
comm "python3", pid 1682, jiffies 4295346908 (age 24.090s)
backtrace:
kmalloc_trace
device_adddevice_private_init at drivers/base/core.c:3361
(inlined by) device_add at drivers/base/core.c:3411
cdev_device_add
gpiolib_cdev_register
gpiochip_setup_dev
gpiochip_add_data_with_key
gcdev_register() & gcdev_unregister() would call device_add() &
device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to
register/unregister device.
However, if device_add() succeeds, some resource (like
struct
GitLab
CVE-2022-3411: A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authe
vendor_gitlab·2023-02-13·CVSS 6.5
CVE-2022-3411 [MEDIUM] CWE-1284 CVE-2022-3411: A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authe
CVE-2022-3411: A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.
Debian
CVE-2022-3411: gitlab - A lack of length validation in GitLab CE/EE affecting all versions from 12.4 bef...
vendor_debian·2022·CVSS 6.5
CVE-2022-3411 [MEDIUM] CVE-2022-3411: gitlab - A lack of length validation in GitLab CE/EE affecting all versions from 12.4 bef...
A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.
Scope: local
sid: resolved (fixed in 15.10.8+ds1-2)
GHSA
GHSA-w4fh-mw73-5c5w: A lack of length validation in GitLab CE/EE affecting all versions from 12
ghsa_unreviewed·2023-02-14
CVE-2022-3411 [MEDIUM] CWE-1284 GHSA-w4fh-mw73-5c5w: A lack of length validation in GitLab CE/EE affecting all versions from 12
A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.
OSV
CVE-2022-3411: A lack of length validation in GitLab CE/EE affecting all versions from 12
osv·2023-02-13·CVSS 6.5
CVE-2022-3411 [MEDIUM] CVE-2022-3411: A lack of length validation in GitLab CE/EE affecting all versions from 12
A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.
No detection rules found.
No public exploits indexed.
arXiv
ICAR, a categorical framework to connect vulnerability, threat and asset managements
arxiv_fulltext·2023-06-21
ICAR, a categorical framework to connect vulnerability, threat and asset managements
1
ICAR, a categorical framework to connect vulnerability, threat and asset managements
[1]Arnaud Valence
[1] ESIEA (Graduate school of digital engineering)
[email protected]
## Abstract
We present ICAR, a mathematical framework derived from category theory for representing cybersecurity NIST and MITRE's ontologies. Designed for cybersecurity, ICAR is a category whose objects are cybersecurity knowledge (weakness, vulnerability, impacted product, attack technique, etc.) and whose morphisms are relations between this knowledge, that make sense for cybersecurity. Within this rigorous and unified framework, we obtain a knowledge graph capable of identifying the attack and weakness structures of an IS, at the interface between description logics, database theory and cybersecurity. We t
Bugzilla
CVE-2022-48975 kernel: gpiolib: fix memory leak in gpiochip_setup_dev()
bugzilla·2024-10-21·CVSS 5.5
CVE-2022-48975 [MEDIUM] CVE-2022-48975 kernel: gpiolib: fix memory leak in gpiochip_setup_dev()
CVE-2022-48975 kernel: gpiolib: fix memory leak in gpiochip_setup_dev()
In the Linux kernel, the following vulnerability has been resolved:
gpiolib: fix memory leak in gpiochip_setup_dev()
Here is a backtrace report about memory leak detected in
gpiochip_setup_dev():
unreferenced object 0xffff88810b406400 (size 512):
comm "python3", pid 1682, jiffies 4295346908 (age 24.090s)
backtrace:
kmalloc_trace
device_add device_private_init at drivers/base/core.c:3361
(inlined by) device_add at drivers/base/core.c:3411
cdev_device_add
gpiolib_cdev_register
gpiochip_setup_dev
gpiochip_add_data_with_key
gcdev_register() & gcdev_unregister() would call device_add() &
device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to
register/unregister device.
However, if device_add() succeeds, some r
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3411.jsonhttps://gitlab.com/gitlab-org/gitlab/-/issues/376247https://hackerone.com/reports/1685995https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3411.jsonhttps://gitlab.com/gitlab-org/gitlab/-/issues/376247https://hackerone.com/reports/1685995
2023-02-13
Published