id
stringlengths 13
16
| published
stringlengths 19
19
| modified
timestamp[ns] | details
stringlengths 30
3.87k
| severity
listlengths 1
1
⌀ | repo_url
stringlengths 23
68
| cwes
sequencelengths 0
1
| commits
sequencelengths 1
4
|
---|---|---|---|---|---|---|---|
CVE-2024-23827 | 2024-01-29T16:15:09 | 2025-01-14T12:11:56.492172 | Nginx-UI is a web interface to manage Nginx configurations. The Import Certificate feature allows arbitrary write into the system. The feature does not check if the provided user input is a certification/key and allows to write into arbitrary paths in the system. It's possible to leverage the vulnerability into a remote code execution overwriting the config file app.ini. Version 2.0.0.beta.12 fixed the issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/0xjacky/nginx-ui | [] | [
"02fb07f6b4885c599e84077078e095a1007dae61"
] |
CVE-2024-22197 | 2024-01-11T18:15:45 | 2025-01-15T05:07:00.916200 | Nginx-ui is online statistics for Server Indicators Monitor CPU usage, memory usage, load average, and disk usage in real-time. The `Home > Preference` page exposes a small list of nginx settings such as `Nginx Access Log Path` and `Nginx Error Log Path`. However, the API also exposes `test_config_cmd`, `reload_cmd` and `restart_cmd`. While the UI doesn't allow users to modify any of these settings, it is possible to do so by sending a request to the API. This issue may lead to authenticated Remote Code Execution, Privilege Escalation, and Information Disclosure. This issue has been patched in version 2.0.0.beta.9. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/0xjacky/nginx-ui | [] | [
"02fb07f6b4885c599e84077078e095a1007dae61"
] |
CVE-2024-22198 | 2024-01-11T20:15:45 | 2025-01-15T05:07:06.192794 | Nginx-UI is a web interface to manage Nginx configurations. It is vulnerable to arbitrary command execution by abusing the configuration settings. The `Home > Preference` page exposes a list of system settings such as `Run Mode`, `Jwt Secret`, `Node Secret` and `Terminal Start Command`. While the UI doesn't allow users to modify the `Terminal Start Command` setting, it is possible to do so by sending a request to the API. This issue may lead to authenticated remote code execution, privilege escalation, and information disclosure. This vulnerability has been patched in version 2.0.0.beta.9. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/0xjacky/nginx-ui | [] | [
"02fb07f6b4885c599e84077078e095a1007dae61"
] |
CVE-2024-22196 | 2024-01-11T20:15:44 | 2025-01-15T05:06:59.257600 | Nginx-UI is an online statistics for Server Indicators Monitor CPU usage, memory usage, load average, and disk usage in real-time. This issue may lead to information disclosure. By using `DefaultQuery`, the `"desc"` and `"id"` values are used as default values if the query parameters are not set. Thus, the `order` and `sort_by` query parameter are user-controlled and are being appended to the `order` variable without any sanitization. This issue has been patched in version 2.0.0.beta.9.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/0xjacky/nginx-ui | [] | [
"02fb07f6b4885c599e84077078e095a1007dae61"
] |
CVE-2024-49367 | 2024-10-21T17:15:03 | 2024-11-07T23:57:17.678334 | Nginx UI is a web user interface for the Nginx web server. Prior to version 2.0.0-beta.36, the log path of nginxui is controllable. This issue can be combined with the directory traversal at `/api/configs` to read directories and file contents on the server. Version 2.0.0-beta.36 fixes the issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/0xjacky/nginx-ui | [] | [
"02fb07f6b4885c599e84077078e095a1007dae61"
] |
CVE-2024-49368 | 2024-10-21T17:15:03 | 2024-11-07T06:57:09.884468 | Nginx UI is a web user interface for the Nginx web server. Prior to version 2.0.0-beta.36, when Nginx UI configures logrotate, it does not verify the input and directly passes it to exec.Command, causing arbitrary command execution. Version 2.0.0-beta.36 fixes this issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/0xjacky/nginx-ui | [] | [
"02fb07f6b4885c599e84077078e095a1007dae61"
] |
CVE-2024-49366 | 2024-10-21T17:15:03 | 2024-11-07T23:57:17.762776 | Nginx UI is a web user interface for the Nginx web server. Nginx UI v2.0.0-beta.35 and earlier gets the value from the json field without verification, and can construct a value value in the form of `../../`. Arbitrary files can be written to the server, which may result in loss of permissions. Version 2.0.0-beta.26 fixes the issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/0xjacky/nginx-ui | [] | [
"02fb07f6b4885c599e84077078e095a1007dae61"
] |
CVE-2023-22478 | 2023-01-14T01:15:14 | 2025-01-15T04:41:08.774311 | KubePi is a modern Kubernetes panel. The API interfaces with unauthorized entities and may leak sensitive information. This issue has been patched in version 1.6.4. There are currently no known workarounds. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/1panel-dev/kubepi | [] | [
"da784f5532ea2495b92708cacb32703bff3a45a3"
] |
CVE-2023-22463 | 2023-01-04T16:15:09 | 2025-01-15T04:41:05.928974 | KubePi is a k8s panel. The jwt authentication function of KubePi through version 1.6.2 uses hard-coded Jwtsigkeys, resulting in the same Jwtsigkeys for all online projects. This means that an attacker can forge any jwt token to take over the administrator account of any online project. Furthermore, they may use the administrator to take over the k8s cluster of the target enterprise. `session.go`, the use of hard-coded JwtSigKey, allows an attacker to use this value to forge jwt tokens arbitrarily. The JwtSigKey is confidential and should not be hard-coded in the code. The vulnerability has been fixed in 1.6.3. In the patch, JWT key is specified in app.yml. If the user leaves it blank, a random key will be used. There are no workarounds aside from upgrading. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/1panel-dev/kubepi | [] | [
"da784f5532ea2495b92708cacb32703bff3a45a3"
] |
CVE-2024-36814 | 2024-10-08T19:15:13 | 2025-02-19T03:37:40.162492 | An arbitrary file read vulnerability in Adguard Home before v0.107.52 allows authenticated attackers to access arbitrary files as root on the underlying Operating System via placing a crafted file into a readable directory. | null | https://github.com/adguardteam/adguardhome | [] | [
"f68f6c9b37cea1f33cb6fa791e6678b9df3a237b"
] |
CVE-2021-27935 | 2021-03-03T20:15:12 | 2025-02-19T03:17:56.091915 | An issue was discovered in AdGuard before 0.105.2. An attacker able to get the user's cookie is able to bruteforce their password offline, because the hash of the password is stored in the cookie. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/adguardteam/adguardhome | [] | [
"f68f6c9b37cea1f33cb6fa791e6678b9df3a237b"
] |
CVE-2019-16060 | 2019-09-06T19:15:11 | 2025-01-14T07:47:12.597146 | The Airbrake Ruby notifier 4.2.3 for Airbrake mishandles the blacklist_keys configuration option and consequently may disclose passwords to unauthorized actors. This is fixed in 4.2.4 (also, 4.2.2 and earlier are unaffected). | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/airbrake/airbrake-ruby | [] | [
"2b63f98566e514f440dba8b107ddc3adc22cba66"
] |
CVE-2024-29192 | 2024-04-04T18:15:14 | 2025-01-15T05:11:31.570211 | gotortc is a camera streaming application. Versions 1.8.5 and prior are vulnerable to Cross-Site Request Forgery. The `/api/config` endpoint allows one to modify the existing configuration with user-supplied values. While the API is only allowing localhost to interact without authentication, an attacker may be able to achieve that depending on how go2rtc is set up on the upstream application, and given that this endpoint is not protected against CSRF, it allows requests from any origin (e.g. a "drive-by" attack) . The `exec` handler allows for any stream to execute arbitrary commands. An attacker may add a custom stream through `api/config`, which may lead to arbitrary command execution. In the event of a victim visiting the server in question, their browser will execute the requests against the go2rtc instance. Commit 8793c3636493c5efdda08f3b5ed5c6e1ea594fd9 adds a warning about secure API access. | null | https://github.com/alexxit/go2rtc | [] | [
"ccec41a10f2636676befea50aa4cee2aa9d1d75a"
] |
CVE-2024-29191 | 2024-04-04T15:15:39 | 2025-01-15T05:11:29.073327 | gotortc is a camera streaming application. Versions 1.8.5 and prior are vulnerable to DOM-based cross-site scripting. The links page (`links.html`) appends the `src` GET parameter (`[0]`) in all of its links for 1-click previews. The context in which `src` is being appended is `innerHTML` (`[1]`), which will insert the text as HTML. Commit 3b3d5b033aac3a019af64f83dec84f70ed2c8aba contains a patch for the issue. | null | https://github.com/alexxit/go2rtc | [] | [
"ccec41a10f2636676befea50aa4cee2aa9d1d75a"
] |
CVE-2024-47067 | 2024-09-30T16:15:09 | 2025-02-19T03:38:38.186655 | AList is a file list program that supports multiple storages. AList contains a reflected cross-site scripting vulnerability in helper.go. The endpoint /i/:link_name takes in a user-provided value and reflects it back in the response. The endpoint returns an application/xml response, opening it up to HTML tags via XHTML and thus leading to a XSS vulnerability. This vulnerability is fixed in 3.29.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/alistgo/alist | [] | [
"a64dd4885ece1709e5287e07dbb4d6832fd1d3b1"
] |
CVE-2020-21485 | 2023-06-20T15:15:11 | 2025-01-14T08:37:58.264245 | Cross Site Scripting vulnerability in Alluxio v.1.8.1 allows a remote attacker to executea arbitrary code via the path parameter in the browse board component. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/alluxio/alluxio | [] | [
"79c6fb4e11e84c08f7866aef97d4e1798f937782"
] |
CVE-2023-38889 | 2023-08-15T17:15:11 | 2025-01-14T11:53:18.572454 | An issue in Alluxio v.2.9.3 and before allows an attacker to execute arbitrary code via a crafted script to the username parameter of lluxio.util.CommonUtils.getUnixGroups(java.lang.String). | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/alluxio/alluxio | [] | [
"79c6fb4e11e84c08f7866aef97d4e1798f937782"
] |
CVE-2022-23848 | 2022-02-20T19:15:09 | 2025-01-14T10:49:34.680272 | In Alluxio before 2.7.3, the logserver does not validate the input stream. NOTE: this is not the same as the CVE-2021-44228 Log4j vulnerability. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/alluxio/alluxio | [] | [
"79c6fb4e11e84c08f7866aef97d4e1798f937782"
] |
CVE-2024-47182 | 2024-09-27T14:15:04 | 2024-10-09T20:59:08.152131 | Dozzle is a realtime log viewer for docker containers. Before version 8.5.3, the app uses sha-256 as the hash for passwords, which leaves users susceptible to rainbow table attacks. The app switches to bcrypt, a more appropriate hash for passwords, in version 8.5.3. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/amir20/dozzle | [] | [
"3c15ac225c5d85701ecbfdae71aad419cf23101d"
] |
CVE-2023-24827 | 2023-02-07T01:15:09 | 2025-01-15T04:44:26.181157 | syft is a a CLI tool and Go library for generating a Software Bill of Materials (SBOM) from container images and filesystems. A password disclosure flaw was found in Syft versions v0.69.0 and v0.69.1. This flaw leaks the password stored in the SYFT_ATTEST_PASSWORD environment variable. The `SYFT_ATTEST_PASSWORD` environment variable is for the `syft attest` command to generate attested SBOMs for the given container image. This environment variable is used to decrypt the private key (provided with `syft attest --key <path-to-key-file>`) during the signing process while generating an SBOM attestation. This vulnerability affects users running syft that have the `SYFT_ATTEST_PASSWORD` environment variable set with credentials (regardless of if the attest command is being used or not). Users that do not have the environment variable `SYFT_ATTEST_PASSWORD` set are not affected by this issue. The credentials are leaked in two ways: in the syft logs when `-vv` or `-vvv` are used in the syft command (which is any log level >= `DEBUG`) and in the attestation or SBOM only when the `syft-json` format is used. Note that as of v0.69.0 any generated attestations by the `syft attest` command are uploaded to the OCI registry (if you have write access to that registry) in the same way `cosign attach` is done. This means that any attestations generated for the affected versions of syft when the `SYFT_ATTEST_PASSWORD` environment variable was set would leak credentials in the attestation payload uploaded to the OCI registry. This issue has been patched in commit `9995950c70` and has been released as v0.70.0. There are no workarounds for this vulnerability. Users are advised to upgrade. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/anchore/syft | [] | [
"1530ef354ffaf59cef6a02c949f2cdb82353954f"
] |
CVE-2021-32721 | 2021-06-29T19:15:09 | 2025-01-14T09:14:44.520045 | PowerMux is a drop-in replacement for Go's http.ServeMux. In PowerMux versions prior to 1.1.1, attackers may be able to craft phishing links and other open redirects by exploiting the trailing slash redirection feature. This may lead to users being redirected to untrusted sites after following an attacker crafted link. The issue is resolved in v1.1.1. There are no existing workarounds. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/andrewburian/powermux | [] | [
"d905ec837601bedbff48f47b476c6e16f232721d"
] |
CVE-2023-39059 | 2023-08-28T22:15:08 | 2025-02-19T03:33:59.662567 | An issue in ansible semaphore v.2.8.90 allows a remote attacker to execute arbitrary code via a crafted payload to the extra variables parameter. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/ansible-semaphore/semaphore | [] | [
"b94cb98ca69e3cf13ac8a830c6fb59e433cd9261"
] |
CVE-2020-25635 | 2020-10-05T14:15:13 | 2025-02-19T03:09:29.286292 | A flaw was found in Ansible Base when using the aws_ssm connection plugin as garbage collector is not happening after playbook run is completed. Files would remain in the bucket exposing the data. This issue affects directly data confidentiality. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/ansible/ansible | [] | [
"0e68601002de5e4e0b06dde6a8f737ebd3312349"
] |
CVE-2020-25636 | 2020-10-05T13:15:13 | 2025-02-19T03:09:29.066662 | A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation for file transfers. Files are written directly to the root bucket, making possible to have collisions when running multiple ansible processes. This issue affects mainly the service availability. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/ansible/ansible | [] | [
"0e68601002de5e4e0b06dde6a8f737ebd3312349"
] |
CVE-2023-1238 | 2023-03-07T08:15:09 | 2025-01-15T04:39:03.838068 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1538 | 2023-03-21T05:15:09 | 2025-01-15T04:40:03.446320 | Observable Timing Discrepancy in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1541 | 2023-03-21T05:15:10 | 2025-01-15T04:39:58.827060 | Business Logic Errors in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1240 | 2023-03-07T08:15:09 | 2025-01-15T04:39:05.361558 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1535 | 2023-03-21T05:15:08 | 2025-01-15T04:39:50.097479 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.7. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1245 | 2023-03-07T08:15:10 | 2025-01-15T04:39:10.254331 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1542 | 2023-03-21T05:15:10 | 2025-01-15T04:39:58.979387 | Business Logic Errors in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1543 | 2023-03-21T05:15:10 | 2025-01-15T04:40:01.589772 | Insufficient Session Expiration in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1540 | 2023-03-21T05:15:09 | 2025-01-15T04:39:59.455006 | Observable Response Discrepancy in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1536 | 2023-03-21T05:15:09 | 2025-01-15T04:39:51.668117 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.7. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1244 | 2023-03-07T08:15:09 | 2025-01-15T04:39:01.406269 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1537 | 2023-03-21T05:15:09 | 2025-01-15T04:39:54.444626 | Authentication Bypass by Capture-replay in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1243 | 2023-03-07T08:15:09 | 2025-01-15T04:39:04.879803 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1239 | 2023-03-07T08:15:09 | 2025-01-15T04:39:12.191260 | Cross-site Scripting (XSS) - Reflected in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1241 | 2023-03-07T08:15:09 | 2025-01-15T04:39:10.757987 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1242 | 2023-03-07T08:15:09 | 2025-01-15T04:39:01.260098 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1237 | 2023-03-07T08:15:08 | 2025-01-15T04:39:03.349819 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1539 | 2023-03-21T05:15:09 | 2025-01-15T04:39:53.428663 | Improper Restriction of Excessive Authentication Attempts in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1975 | 2023-04-11T10:15:18 | 2025-01-15T04:40:45.424521 | Insertion of Sensitive Information Into Sent Data in GitHub repository answerdev/answer prior to 1.0.8. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1976 | 2023-04-11T11:15:08 | 2025-01-15T04:40:57.059996 | Password Aging with Long Expiration in GitHub repository answerdev/answer prior to 1.0.6. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-1974 | 2023-04-11T10:15:17 | 2025-01-15T04:40:44.950887 | Exposure of Sensitive Information Through Metadata in GitHub repository answerdev/answer prior to 1.0.8. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-4127 | 2023-08-03T04:15:11 | 2025-01-15T04:57:48.860168 | Race Condition within a Thread in GitHub repository answerdev/answer prior to v1.1.1. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-4125 | 2023-08-03T04:15:11 | 2025-01-15T04:57:51.490731 | Weak Password Requirements in GitHub repository answerdev/answer prior to v1.1.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-4124 | 2023-08-03T04:15:11 | 2025-01-15T04:57:45.774820 | Missing Authorization in GitHub repository answerdev/answer prior to v1.1.1. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-4126 | 2023-08-03T04:15:11 | 2025-01-15T04:57:50.702051 | Insufficient Session Expiration in GitHub repository answerdev/answer prior to v1.1.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-4815 | 2023-09-07T07:15:08 | 2025-01-15T05:01:24.289895 | Missing Authentication for Critical Function in GitHub repository answerdev/answer prior to v1.1.3. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-0739 | 2023-02-08T05:15:11 | 2025-01-15T04:34:49.667529 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in GitHub repository answerdev/answer prior to 1.0.4. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-0740 | 2023-02-08T08:15:08 | 2025-01-15T04:34:29.435741 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.4. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-0743 | 2023-02-08T08:15:08 | 2025-01-15T04:34:34.948525 | Cross-site Scripting (XSS) - Generic in GitHub repository answerdev/answer prior to 1.0.4. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-0934 | 2023-02-21T15:15:12 | 2025-01-15T04:38:30.328525 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.5. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-0742 | 2023-02-08T08:15:08 | 2025-01-15T04:34:39.337402 | Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.4. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-0744 | 2023-02-08T08:15:08 | 2025-01-15T04:34:59.140408 | Improper Access Control in GitHub repository answerdev/answer prior to 1.0.4. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-0741 | 2023-02-08T08:15:08 | 2025-01-15T04:34:52.227959 | Cross-site Scripting (XSS) - DOM in GitHub repository answerdev/answer prior to 1.0.4. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2023-2590 | 2023-05-09T06:15:08 | 2025-01-15T04:46:15.979696 | Missing Authorization in GitHub repository answerdev/answer prior to 1.0.9. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/answerdev/answer | [] | [
"f2046190d6a399a115a214b1d62c4c291ac7d03c"
] |
CVE-2021-33190 | 2021-06-08T15:15:08 | 2025-01-14T09:16:03.067968 | In Apache APISIX Dashboard version 2.6, we changed the default value of listen host to 0.0.0.0 in order to facilitate users to configure external network access. In the IP allowed list restriction, a risky function was used for the IP acquisition, which made it possible to bypass the network limit. At the same time, the default account and password are fixed.Ultimately these factors lead to the issue of security risks. This issue is fixed in APISIX Dashboard 2.6.1 | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apache/apisix-dashboard | [] | [
"c574813eea82edcd6d95a2ea0f8857b736049717"
] |
CVE-2021-45232 | 2021-12-27T15:15:07 | 2025-02-19T03:22:27.483001 | In Apache APISIX Dashboard before 2.10.1, the Manager API uses two frameworks and introduces framework `droplet` on the basis of framework `gin`, all APIs and authentication middleware are developed based on framework `droplet`, but some API directly use the interface of framework `gin` thus bypassing the authentication. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/apache/apisix-dashboard | [] | [
"c574813eea82edcd6d95a2ea0f8857b736049717"
] |
CVE-2023-26512 | 2023-07-17T08:15:09 | 2025-02-08T01:53:55.225511 | CWE-502 Deserialization of Untrusted Data at the rabbitmq-connector plugin module in Apache EventMesh (incubating) V1.7.0\V1.8.0 on windows\linux\mac os e.g. platforms allows attackers to send controlled message and
remote code execute via rabbitmq messages. Users can use the code under the master branch in project repo to fix this issue, we will release the new version as soon as possible. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/apache/eventmesh | [] | [
"63ac4ec808933a64b048a3988f6c91671d2bc41a"
] |
CVE-2023-49619 | 2024-01-10T09:15:44 | 2025-01-14T12:06:17.335800 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Answer.
This issue affects Apache Answer: through 1.2.0.
Under normal circumstances, a user can only bookmark a question once, and will only increase the number of questions bookmarked once. However, repeat submissions through the script can increase the number of collection of the question many times.
Users are recommended to upgrade to version [1.2.1], which fixes the issue. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-answer | [] | [
"8a3b19fd32fabae4eed98a1f240a01f27bebdf5f"
] |
CVE-2024-41888 | 2024-08-12T13:38:31 | 2025-01-14T12:17:10.491121 | Missing Release of Resource after Effective Lifetime vulnerability in Apache Answer.
This issue affects Apache Answer: through 1.3.5.
The password reset link remains valid within its expiration period even after it has been used. This could potentially lead to the link being misused or hijacked.
Users are recommended to upgrade to version 1.3.6, which fixes the issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-answer | [] | [
"8a3b19fd32fabae4eed98a1f240a01f27bebdf5f"
] |
CVE-2024-41890 | 2024-08-12T13:38:31 | 2025-01-14T12:18:15.627980 | Missing Release of Resource after Effective Lifetime vulnerability in Apache Answer.
This issue affects Apache Answer: through 1.3.5.
User sends multiple password reset emails, each containing a valid link. Within the link's validity period, this could potentially lead to the link being misused or hijacked.
Users are recommended to upgrade to version 1.3.6, which fixes the issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-answer | [] | [
"8a3b19fd32fabae4eed98a1f240a01f27bebdf5f"
] |
CVE-2024-26578 | 2024-02-22T10:15:08 | 2025-02-13T19:47:28.902943 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Answer.This issue affects Apache Answer: through 1.2.1.
Repeated submission during registration resulted in the registration of the same user. When users register, if they rapidly submit multiple registrations using scripts, it can result in the creation of multiple user accounts simultaneously with the same name.
Users are recommended to upgrade to version [1.2.5], which fixes the issue. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-answer | [] | [
"8a3b19fd32fabae4eed98a1f240a01f27bebdf5f"
] |
CVE-2024-23349 | 2024-02-22T10:15:08 | 2025-01-15T05:07:49.383911 | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache Answer.This issue affects Apache Answer: through 1.2.1.
XSS attack when user enters summary. A logged-in user, when modifying their own submitted question, can input malicious code in the summary to create such an attack.
Users are recommended to upgrade to version [1.2.5], which fixes the issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-answer | [] | [
"8a3b19fd32fabae4eed98a1f240a01f27bebdf5f"
] |
CVE-2021-24117 | 2021-07-14T14:15:08 | 2025-01-15T01:47:51.455770 | In Apache Teaclave Rust SGX SDK 1.1.3, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be single stepped, especially Intel SGX. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-teaclave-sgx-sdk | [] | [
"bc2d7e245679423312be2deb51701587b4070681"
] |
CVE-2020-5499 | 2020-01-04T07:15:11 | 2025-01-14T08:47:42.557541 | Baidu Rust SGX SDK through 1.0.8 has an enclave ID race. There are non-deterministic results in which, sometimes, two global IDs are the same. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-teaclave-sgx-sdk | [] | [
"bc2d7e245679423312be2deb51701587b4070681"
] |
CVE-2021-43350 | 2021-11-11T13:15:07 | 2025-01-14T10:00:35.339901 | An unauthenticated Apache Traffic Control Traffic Ops user can send a request with a specially-crafted username to the POST /login endpoint of any API version to inject unsanitized content into the LDAP filter. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-trafficcontrol | [] | [
"a52ae6cda73ef477aec691b0d27701326d20e025"
] |
CVE-2022-23206 | 2022-02-06T16:15:07 | 2025-01-14T10:47:39.253390 | In Apache Traffic Control Traffic Ops prior to 6.1.0 or 5.1.6, an unprivileged user who can reach Traffic Ops over HTTPS can send a specially-crafted POST request to /user/login/oauth to scan a port of a server that Traffic Ops can reach. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apache/incubator-trafficcontrol | [] | [
"a52ae6cda73ef477aec691b0d27701326d20e025"
] |
CVE-2023-46302 | 2023-11-20T09:15:07 | 2025-01-14T12:02:36.924593 | Apache Software Foundation Apache Submarine has a bug when serializing against yaml. The bug is caused by snakeyaml https://nvd.nist.gov/vuln/detail/CVE-2022-1471 .
Apache Submarine uses JAXRS to define REST endpoints. In order to
handle YAML requests (using application/yaml content-type), it defines
a YamlEntityProvider entity provider that will process all incoming
YAML requests. In order to unmarshal the request, the readFrom method
is invoked, passing the entityStream containing the user-supplied data in `submarine-server/server-core/src/main/java/org/apache/submarine/server/utils/YamlUtils.java`.
We have now fixed this issue in the new version by replacing to `jackson-dataformat-yaml`.
This issue affects Apache Submarine: from 0.7.0 before 0.8.0. Users are recommended to upgrade to version 0.8.0, which fixes this issue.
If using the version smaller than 0.8.0 and not want to upgrade, you can try cherry-pick PR https://github.com/apache/submarine/pull/1054 and rebuild the submart-server image to fix this.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/apache/submarine | [] | [
"e7c6a546b8db2d168c3dfa4a6c99b07601887ec3"
] |
CVE-2023-37924 | 2023-11-22T10:15:07 | 2025-01-14T11:49:55.641232 | Apache Software Foundation Apache Submarine has an SQL injection vulnerability when a user logs in. This issue can result in unauthorized login.
Now we have fixed this issue and now user must have the correct login to access workbench.
This issue affects Apache Submarine: from 0.7.0 before 0.8.0. We recommend that all submarine users with 0.7.0 upgrade to 0.8.0, which not only fixes the issue, supports the oidc authentication mode, but also removes the case of unauthenticated logins.
If using the version lower than 0.8.0 and not want to upgrade, you can try cherry-pick PR https://github.com/apache/submarine/pull/1037 https://github.com/apache/submarine/pull/1054 and rebuild the submarine-server image to fix this.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/apache/submarine | [] | [
"e7c6a546b8db2d168c3dfa4a6c99b07601887ec3"
] |
CVE-2023-30549 | 2023-04-25T21:15:10 | 2025-01-15T05:09:55.730799 | Apptainer is an open source container platform for Linux. There is an ext4 use-after-free flaw that is exploitable through versions of Apptainer < 1.1.0 and installations that include apptainer-suid < 1.1.8 on older operating systems where that CVE has not been patched. That includes Red Hat Enterprise Linux 7, Debian 10 buster (unless the linux-5.10 package is installed), Ubuntu 18.04 bionic and Ubuntu 20.04 focal. Use-after-free flaws in the kernel can be used to attack the kernel for denial of service and potentially for privilege escalation.
Apptainer 1.1.8 includes a patch that by default disables mounting of extfs filesystem types in setuid-root mode, while continuing to allow mounting of extfs filesystems in non-setuid "rootless" mode using fuse2fs.
Some workarounds are possible. Either do not install apptainer-suid (for versions 1.1.0 through 1.1.7) or set `allow setuid = no` in apptainer.conf. This requires having unprivileged user namespaces enabled and except for apptainer 1.1.x versions will disallow mounting of sif files, extfs files, and squashfs files in addition to other, less significant impacts. (Encrypted sif files are also not supported unprivileged in apptainer 1.1.x.). Alternatively, use the `limit containers` options in apptainer.conf/singularity.conf to limit sif files to trusted users, groups, and/or paths, and set `allow container extfs = no` to disallow mounting of extfs overlay files. The latter option by itself does not disallow mounting of extfs overlay partitions inside SIF files, so that's why the former options are also needed. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/apptainer/apptainer | [] | [
"744c94b5837d34d12d15cb87298b989b3c77f050"
] |
CVE-2023-38496 | 2023-07-25T22:15:10 | 2025-01-14T11:50:25.093195 | Apptainer is an open source container platform. Version 1.2.0-rc.2 introduced an ineffective privilege drop when requesting container network setup, therefore subsequent functions are called with root privileges, the attack surface is rather limited for users but an attacker could possibly craft a starter config to delete any directory on the host filesystems. A security fix has been included in Apptainer 1.2.1. There is no known workaround outside of upgrading to Apptainer 1.2.1. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apptainer/apptainer | [] | [
"744c94b5837d34d12d15cb87298b989b3c77f050"
] |
CVE-2020-15229 | 2020-10-14T19:15:13 | 2025-01-15T01:43:17.478984 | Singularity (an open source container platform) from version 3.1.1 through 3.6.3 has a vulnerability. Due to insecure handling of path traversal and the lack of path sanitization within `unsquashfs`, it is possible to overwrite/create any files on the host filesystem during the extraction with a crafted squashfs filesystem. The extraction occurs automatically for unprivileged (either installation or with `allow setuid = no`) run of Singularity when a user attempt to run an image which is a local SIF image or a single file containing a squashfs filesystem and is coming from remote sources `library://` or `shub://`. Image build is also impacted in a more serious way as it can be used by a root user, allowing an attacker to overwrite/create files leading to a system compromise, so far bootstrap methods `library`, `shub` and `localimage` are triggering the squashfs extraction. This issue is addressed in Singularity 3.6.4. All users are advised to upgrade to 3.6.4 especially if they use Singularity mainly for building image as root user. There is no solid workaround except to temporary avoid to use unprivileged mode with single file images in favor of sandbox images instead. Regarding image build, temporary avoid to build from `library` and `shub` sources and as much as possible use `--fakeroot` or a VM for that. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/apptainer/singularity | [] | [
"98ad49a3de9043ea287d65f4d544632ff074e506"
] |
CVE-2023-42374 | 2024-02-13T01:15:07 | 2025-01-15T05:04:44.918794 | An issue in mystenlabs Sui Blockchain before v.1.6.3 allow a remote attacker to execute arbitrary code and cause a denial of service via a crafted compressed script to the Sui node component. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aptos-labs/aptos-core | [] | [
"6b610f4fc36098662dd0742ecc16687b8b535bb3"
] |
CVE-2023-36184 | 2023-09-08T02:15:08 | 2025-01-15T04:56:09.741847 | CMysten Labs Sui blockchain v1.2.0 was discovered to contain a stack overflow via the component /spec/openrpc.json. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aptos-labs/aptos-core | [] | [
"6b610f4fc36098662dd0742ecc16687b8b535bb3"
] |
CVE-2024-35192 | 2024-05-20T21:15:09 | 2025-01-15T05:14:40.531620 | Trivy is a security scanner. Prior to 0.51.2, if a malicious actor is able to trigger Trivy to scan container images from a crafted malicious registry, it could result in the leakage of credentials for legitimate registries such as AWS Elastic Container Registry (ECR), Google Cloud Artifact/Container Registry, or Azure Container Registry (ACR). These tokens can then be used to push/pull images from those registries to which the identity/user running Trivy has access. Systems are not affected if the default credential provider chain is unable to obtain valid credentials. This vulnerability only applies when scanning container images directly from a registry. This vulnerability is fixed in 0.51.2. | null | https://github.com/aquasecurity/trivy | [] | [
"8016b821a260840ccb81ef520f2804b9482f3820"
] |
CVE-2023-43802 | 2023-10-18T21:15:09 | 2025-01-14T12:00:01.681472 | Arduino Create Agent is a package to help manage Arduino development. This vulnerability affects the endpoint `/upload` which handles request with the `filename` parameter. A user who has the ability to perform HTTP requests to the localhost interface, or is able to bypass the CORS configuration, can escalate their privileges to those of the user running the Arduino Create Agent service via a crafted HTTP POST request. This issue has been addressed in version `1.3.3`. Users are advised to upgrade. There are no known workarounds for this vulnerability. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/arduino/arduino-create-agent | [] | [
"d170a5e8d36292dfb95387d0d345d2b279b6c224"
] |
CVE-2023-43801 | 2023-10-18T22:15:09 | 2025-01-14T12:00:01.498339 | Arduino Create Agent is a package to help manage Arduino development. This vulnerability affects the endpoint `/v2/pkgs/tools/installed` and the way it handles plugin names supplied as user input. A user who has the ability to perform HTTP requests to the localhost interface, or is able to bypass the CORS configuration, can delete arbitrary files or folders belonging to the user that runs the Arduino Create Agent via a crafted HTTP DELETE request. This issue has been addressed in version `1.3.3`. Users are advised to upgrade. There are no known workarounds for this issue.
| [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/arduino/arduino-create-agent | [] | [
"d170a5e8d36292dfb95387d0d345d2b279b6c224"
] |
CVE-2023-43800 | 2023-10-18T22:15:09 | 2025-01-14T11:59:58.705773 | Arduino Create Agent is a package to help manage Arduino development. The vulnerability affects the endpoint `/v2/pkgs/tools/installed`. A user who has the ability to perform HTTP requests to the localhost interface, or is able to bypass the CORS configuration, can escalate his privileges to those of the user running the Arduino Create Agent service via a crafted HTTP POST request. This issue has been addressed in version `1.3.3`. Users are advised to upgrade. There are no known workarounds for this issue. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/arduino/arduino-create-agent | [] | [
"d170a5e8d36292dfb95387d0d345d2b279b6c224"
] |
CVE-2023-43803 | 2023-10-18T21:15:09 | 2025-01-14T12:00:00.918887 | Arduino Create Agent is a package to help manage Arduino development. This vulnerability affects the endpoint `/v2/pkgs/tools/installed` and the way it handles plugin names supplied as user input. A user who has the ability to perform HTTP requests to the localhost interface, or is able to bypass the CORS configuration, can delete arbitrary files or folders belonging to the user that runs the Arduino Create Agent via a crafted HTTP POST request. This issue has been addressed in version `1.3.3`. Users are advised to upgrade. There are no known workarounds for this vulnerability. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/arduino/arduino-create-agent | [] | [
"d170a5e8d36292dfb95387d0d345d2b279b6c224"
] |
CVE-2023-49296 | 2023-12-13T20:15:49 | 2025-01-15T05:01:57.947479 | The Arduino Create Agent allows users to use the Arduino Create applications to upload code to any USB connected Arduino board directly from the browser. A vulnerability in versions prior to 1.3.6 affects the endpoint `/certificate.crt` and the way the web interface of the ArduinoCreateAgent handles custom error messages. An attacker that is able to persuade a victim into clicking on a malicious link can perform a Reflected Cross-Site Scripting attack on the web interface of the create agent, which would allow the attacker to execute arbitrary browser client side code. Version 1.3.6 contains a fix for the issue.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/arduino/arduino-create-agent | [] | [
"d170a5e8d36292dfb95387d0d345d2b279b6c224"
] |
CVE-2022-25856 | 2022-06-17T20:15:10 | 2025-01-15T02:19:10.176988 | The package github.com/argoproj/argo-events/sensors/artifacts before 1.7.1 are vulnerable to Directory Traversal in the (g *GitArtifactReader).Read() API in git.go. This could allow arbitrary file reads if the GitArtifactReader is provided a pathname containing a symbolic link or an implicit directory name such as ... | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/argoproj/argo-events | [] | [
"6b10ce4d463c312085fb33f6be12cfd137ea19bc"
] |
CVE-2022-31054 | 2022-06-13T20:15:07 | 2025-01-15T02:21:33.287385 | Argo Events is an event-driven workflow automation framework for Kubernetes. Prior to version 1.7.1, several `HandleRoute` endpoints make use of the deprecated `ioutil.ReadAll()`. `ioutil.ReadAll()` reads all the data into memory. As such, an attacker who sends a large request to the Argo Events server will be able to crash it and cause denial of service. A patch for this vulnerability has been released in Argo Events version 1.7.1. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/argoproj/argo-events | [] | [
"6b10ce4d463c312085fb33f6be12cfd137ea19bc"
] |
CVE-2024-47827 | 2024-10-28T16:15:03 | 2024-11-05T18:46:49.986249 | Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Due to a race condition in a global variable in 3.6.0-rc1, the argo workflows controller can be made to crash on-command by any user with access to execute a workflow. This vulnerability is fixed in 3.6.0-rc2. | [
{
"score": "CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/argoproj/argo-workflows | [] | [
"3fff791e4ef5b7e1de82ccb36cae327e8eb726f6"
] |
CVE-2021-37914 | 2021-08-03T00:15:08 | 2025-01-14T09:29:07.952896 | In Argo Workflows through 3.1.3, if EXPRESSION_TEMPLATES is enabled and untrusted users are allowed to specify input parameters when running workflows, an attacker may be able to disrupt a workflow because expression template output is evaluated. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L",
"type": "CVSS_V3"
}
] | https://github.com/argoproj/argo-workflows | [] | [
"3fff791e4ef5b7e1de82ccb36cae327e8eb726f6"
] |
CVE-2022-29164 | 2022-05-06T00:15:07 | 2025-01-15T02:20:25.712782 | Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. In affected versions an attacker can create a workflow which produces a HTML artifact containing an HTML file that contains a script which uses XHR calls to interact with the Argo Server API. The attacker emails the deep-link to the artifact to their victim. The victim opens the link, the script starts running. As the script has access to the Argo Server API (as the victim), so may read information about the victim’s workflows, or create and delete workflows. Note the attacker must be an insider: they must have access to the same cluster as the victim and must already be able to run their own workflows. The attacker must have an understanding of the victim’s system. We have seen no evidence of this in the wild. We urge all users to upgrade to the fixed versions. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/argoproj/argo-workflows | [] | [
"3fff791e4ef5b7e1de82ccb36cae327e8eb726f6"
] |
CVE-2023-45821 | 2023-10-19T21:15:08 | 2025-02-19T03:33:07.655525 | Artifact Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. During a security audit of Artifact Hub's code base a security researcher identified a bug in which the `registryIsDockerHub` function was only checking that the registry domain had the `docker.io` suffix. Artifact Hub allows providing some Docker credentials that are used to increase the rate limit applied when interacting with the Docker Hub registry API to read publicly available content. Due to the incorrect check described above, it'd be possible to hijack those credentials by purchasing a domain which ends with `docker.io` and deploying a fake OCI registry on it. <https://artifacthub.io/> uses some credentials that only have permissions to read public content available in the Docker Hub. However, even though credentials for private repositories (disabled on `artifacthub.io`) are handled in a different way, other Artifact Hub deployments could have been using them for a different purpose. This issue has been resolved in version `1.16.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
] | https://github.com/artifacthub/hub | [] | [
"053763fcbf1b9ceca27e1b8e42bd07e2b44fc32b"
] |
CVE-2023-45823 | 2023-10-19T21:15:09 | 2025-02-19T03:33:12.274242 | Artifact Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. During a security audit of Artifact Hub's code base a security researcher identified a bug in which by using symbolic links in certain kinds of repositories loaded into Artifact Hub, it was possible to read internal files. Artifact Hub indexes content from a variety of sources, including git repositories. When processing git based repositories, Artifact Hub clones the repository and, depending on the artifact kind, reads some files from it. During this process, in some cases, no validation was done to check if the file was a symbolic link. This made possible to read arbitrary files in the system, potentially leaking sensitive information. This issue has been resolved in version `1.16.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/artifacthub/hub | [] | [
"053763fcbf1b9ceca27e1b8e42bd07e2b44fc32b"
] |
CVE-2023-45822 | 2023-10-19T21:15:08 | 2025-02-19T03:33:05.618496 | Artifact Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. During a security audit of Artifact Hub's code base a security researcher identified a bug in which a default unsafe rego built-in was allowed to be used when defining authorization policies. Artifact Hub includes a fine-grained authorization mechanism that allows organizations to define what actions can be performed by their members. It is based on customizable authorization policies that are enforced by the `Open Policy Agent`. Policies are written using `rego` and their data files are expected to be json documents. By default, `rego` allows policies to make HTTP requests, which can be abused to send requests to internal resources and forward the responses to an external entity. In the context of Artifact Hub, this capability should have been disabled. This issue has been resolved in version `1.16.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/artifacthub/hub | [] | [
"053763fcbf1b9ceca27e1b8e42bd07e2b44fc32b"
] |
CVE-2022-36006 | 2022-08-15T11:21:40 | 2025-01-14T11:03:16.103925 | Arvados is an open source platform for managing, processing, and sharing genomic and other large scientific and biomedical data. A remote code execution (RCE) vulnerability in the Arvados Workbench allows authenticated attackers to execute arbitrary code via specially crafted JSON payloads. This exists in all versions up to 2.4.1 and is fixed in 2.4.2. This vulnerability is specific to the Ruby on Rails Workbench application (“Workbench 1”). We do not believe any other Arvados components, including the TypesScript browser-based Workbench application (“Workbench 2”) or API Server, are vulnerable to this attack. For versions of Arvados earlier than 2.4.2: remove the Ruby-based "Workbench 1" app ("apt-get remove arvados-workbench") from your installation as a workaround. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/arvados/arvados | [] | [
"9393327642b82d15c195a32a7b007a30c9e6d07b"
] |
CVE-2022-39238 | 2022-09-23T08:15:09 | 2025-01-14T11:06:39.945629 | Arvados is an open source platform for managing and analyzing biomedical big data. In versions prior to 2.4.3, when using Portable Authentication Modules (PAM) for user authentication, if a user presented valid credentials but the account is disabled or otherwise not allowed to access the host (such as an expired password), it would still be accepted for access to Arvados. Other authentication methods (LDAP, OpenID Connect) supported by Arvados are not affected by this flaw. This issue is patched in version 2.4.3. Workaround for this issue is to migrate to a different authentication method supported by Arvados, such as LDAP. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/arvados/arvados | [] | [
"9393327642b82d15c195a32a7b007a30c9e6d07b"
] |
CVE-2019-16355 | 2019-09-16T15:15:10 | 2025-02-19T02:52:19.248919 | The File Session Manager in Beego 1.10.0 allows local users to read session files because of weak permissions for individual files. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/astaxie/beego | [] | [
"a09bafbf2ab483742b17bb352f95dbc0a597e720"
] |
CVE-2019-16354 | 2019-09-16T15:15:10 | 2025-02-19T02:52:15.645442 | The File Session Manager in Beego 1.10.0 allows local users to read session files because there is a race condition involving file creation within a directory with weak permissions. | [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/astaxie/beego | [] | [
"a09bafbf2ab483742b17bb352f95dbc0a597e720"
] |
CVE-2021-29456 | 2021-04-21T19:15:35 | 2025-02-19T03:18:21.882684 | Authelia is an open-source authentication and authorization server providing 2-factor authentication and single sign-on (SSO) for your applications via a web portal. In versions 4.27.4 and earlier, utilizing a HTTP query parameter an attacker is able to redirect users from the web application to any domain, including potentially malicious sites. This security issue does not directly impact the security of the web application itself. As a workaround, one can use a reverse proxy to strip the query parameter from the affected endpoint. There is a patch for version 4.28.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/authelia/authelia | [] | [
"6ea62657d90ce480780befdc4284bf0d79be1e07"
] |
CVE-2021-32637 | 2021-05-28T17:15:07 | 2025-01-15T01:54:17.696804 | Authelia is a a single sign-on multi-factor portal for web apps. This affects uses who are using nginx ngx_http_auth_request_module with Authelia, it allows a malicious individual who crafts a malformed HTTP request to bypass the authentication mechanism. It additionally could theoretically affect other proxy servers, but all of the ones we officially support except nginx do not allow malformed URI paths. The problem is rectified entirely in v4.29.3. As this patch is relatively straightforward we can back port this to any version upon request. Alternatively we are supplying a git patch to 4.25.1 which should be relatively straightforward to apply to any version, the git patches for specific versions can be found in the references. The most relevant workaround is upgrading. You can also add a block which fails requests that contains a malformed URI in the internal location block. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/authelia/authelia | [] | [
"6ea62657d90ce480780befdc4284bf0d79be1e07"
] |
CVE-2025-24806 | 2025-02-19T18:15:24 | 2025-02-20T08:55:15.346912 | Authelia is an open-source authentication and authorization server providing two-factor authentication and single sign-on (SSO) for applications via a web portal. If users are allowed to sign in via both username and email the regulation system treats these as separate login events. This leads to the regulation limitations being effectively doubled assuming an attacker using brute-force to find a user password. It's important to note that due to the effective operation of regulation where no user-facing sign of their regulation ban being visible either via timing or via API responses, it's effectively impossible to determine if a failure occurs due to a bad username password combination, or a effective ban blocking the attempt which heavily mitigates any form of brute-force. This occurs because the records and counting process for this system uses the method utilized for sign in rather than the effective username attribute. This has a minimal impact on account security, this impact is increased naturally in scenarios when there is no two-factor authentication required and weak passwords are used. This makes it a bit easier to brute-force a password. A patch for this issue has been applied to versions 4.38.19, and 4.39.0. Users are advised to upgrade. Users unable to upgrade should 1. Not heavily modify the default settings in a way that ends up with shorter or less frequent regulation bans. The default settings effectively mitigate any potential for this issue to be exploited. and 2. Disable the ability for users to login via an email address. | null | https://github.com/authelia/authelia | [] | [
"6ea62657d90ce480780befdc4284bf0d79be1e07"
] |
CVE-2024-27101 | 2024-03-01T21:15:08 | 2025-01-15T05:10:03.647169 | SpiceDB is an open source, Google Zanzibar-inspired database for creating and managing security-critical application permissions. Integer overflow in chunking helper causes dispatching to miss elements or panic. Any SpiceDB cluster with any schema where a resource being checked has more than 65535 relationships for the same resource and subject type is affected by this problem. The CheckPermission, BulkCheckPermission, and LookupSubjects API methods are affected. This vulnerability is fixed in 1.29.2. | null | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
CVE-2024-32001 | 2024-04-10T23:15:07 | 2025-01-15T05:12:26.817957 | SpiceDB is a graph database purpose-built for storing and evaluating access control data. Use of a relation of the form: `relation folder: folder | folder#parent` with an arrow such as `folder->view` can cause LookupSubjects to only return the subjects found under subjects for either `folder` or `folder#parent`. This bug only manifests if the same subject type is used multiple types in a relation, relationships exist for both subject types and an arrow is used over the relation. Any user making a negative authorization decision based on the results of a LookupSubjects request with version before v1.30.1 is affected. Version 1.30.1 contains a patch for the issue. As a workaround, avoid using LookupSubjects for negative authorization decisions and/or avoid using the broken schema.
| null | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
Subsets and Splits