The Chartkick gem for Ruby allows Cascading Style Sheets (CSS) Injection (without attribute).
A denial of service vulnerability exists in Fastify that allows a malicious user to trigger resource exhaustion (when the `allErrors` option is used) with specially crafted schemas.
The Field Test gem for Ruby allows CSRF.
In TYPO3 installations with the `mediace` extension, it has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. The allows to inject arbitrary data having a valid cryptographic message authentication code and can lead to remote code execution. To successfully exploit this vulnerability, an attacker must have access to at least one `Extbase` plugin or module action in a TYPO3 installation.
In TYPO3 CMS, it has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains including potential privilege escalation, insecure deserialization & remote code execution. The overall severity of this vulnerability is high based on mentioned attack chains and the requirement of having a valid backend user session (authenticated).
The DAO/DTO implementation in SpringBlade through allows SQL Injection in an ORDER BY clause. This is related to the `/api/blade-log/api/list` `ascs` and `desc` parameters.
In TYPO3 CMS, in a case where an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1), it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch `typo3conf/LocalConfiguration.php`, which again contains the `encryptionKey` as well as credentials of the database management system being used. In case a database server is directly accessible either via internet or in a shared hosting network, this allows the ability to completely retrieve, manipulate or delete database contents. This includes creating an administration user account which can be used to trigger remote code execution by injecting custom extensions.
The Kubernetes API server component has been found to be vulnerable to a denial of service attack via successful API requests.
The Kubernetes kube-apiserver is vulnerable to an unvalidated redirect on proxied upgrade requests that could allow an attacker to escalate privileges from a node compromise to a full cluster compromise.
The Kubernetes ingress-nginx component allows a user with the ability to create namespaces and to read and create ingress objects to overwrite the password file of another ingress which uses `nginx.ingress.kubernetes.io/auth-type`.
In OctoberCMS, encrypted cookie values were not tied to the name of the cookie the value belonged to. This meant that certain classes of attacks that took advantage of other theoretical vulnerabilities in user facing code (nothing exploitable in the core project itself) had a higher chance of succeeding. Specifically, if your usage exposed a way for users to provide unfiltered user input and have it returned to them as an encrypted cookie (ex. storing a user provided search query in a cookie) they could then use the generated cookie in place of other more tightly controlled cookies; or if your usage exposed the plaintext version of an encrypted cookie at any point to the user they could theoretically provide encrypted content from your application back to it as an encrypted cookie and force the framework to decrypt it for them.
In auth0 (npm package), a DenyList of specific keys that should be sanitized from the request object contained in the error object is used. The key for Authorization header is not sanitized and in certain cases the Authorization header value can be logged exposing a bearer token. You are affected by this vulnerability if you are using the auth0 npm package, and you are using a Machine to Machine application authorized to use Auth0's management API.
In SLP Validate (npm package slp-validate), there is a vulnerability to false-positive validation outcomes for the NFT1 Child Genesis transaction type. A poorly implemented SLP wallet or opportunistic attacker could create a seemingly valid NFT1 child token without burning any of the NFT1 Group token type as is required by the NFT1 specification.
Virtual Machine Instances (VMIs) can be used to gain access to the host's filesystem. Successful exploitation allows an attacker to assume the privileges of the VM process on the host system. In worst-case scenarios an attacker can read and modify any file on the system where the VMI is running. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
This affects the package express-fileupload. If the `parseNested` option is enabled, sending a corrupt HTTP request can lead to denial of service or arbitrary code execution.
The request logger provided by the package is vulnerable to ASNI escape sequence injection. Whenever any HTTP request is received, the default behaviour of uvicorn is to log its details to either the console or a log file. When attackers request crafted URLs with percent-encoded escape sequences, the logging component will log the URL after it's been processed with `urllib.parse.unquote`, therefore converting any percent-encoded characters into their single-character equivalent, which can have special meaning in terminal emulators.
The Kubelet component in versions 1.15.0-1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via the kubelet API, including the unauthenticated HTTP read-only API typically served on port 10255, and the authenticated HTTPS API typically served on port 10250.
In SLPJS (npm package slpjs), there is a vulnerability to false-positive validation outcomes for the NFT1 Child Genesis transaction type. A poorly implemented SLP wallet or opportunistic attacker could create a seemingly valid NFT1 child token without burning any of the NFT1 Group token type as is required by the NFT1 specification.
In Shopware, the database password is leaked to an unauthenticated user when a `DriverException` occurs and verbose error handling is enabled.
The Gerapy suffers from an OS command injection vulnerability. Unsanitized input is passed to `Popen`, via the `project_configure` endpoint.
Shopware is vulnerable to a Server-Side Request Forgery (SSRF) in its "Mediabrowser upload by URL" feature. This allows an authenticated user to send HTTP, HTTPS, FTP, and SFTP requests on behalf of the Shopware platform server.
In Shopware, authenticated users are allowed to use the Mediabrowser fileupload feature to upload SVG images containing JavaScript. This leads to Persistent XSS. An uploaded image can be accessed without authentication.
The `/etc/hosts` file mounted in a pod by kubelet is not included by the kubelet eviction manager when calculating ephemeral storage usage by a pod. If a pod writes a large amount of data to the `/etc/hosts` file, it could fill the storage space of the node and cause the node to fail.
The dlf (aka `Kitodo.Presentation`) for TYPO3 allows XSS.
Lua has a segmentation fault in `changedline` in `ldebug.c` (e.g., when called by `luaG_traceexec`) because it incorrectly expects that an `oldpc` value is always updated upon a return of the flow of control to a function.
A Cross-Site Scripting (XSS) vulnerability in the `munki_facts` (aka Munki Conditions) module for `MunkiReport` allows remote attackers to inject arbitrary web script or HTML via the key name.
kube-proxy was found to contain a security issue which allows adjacent hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace. Such a service is generally thought to be reachable only by other processes on the same host, but due to this defeect, could be reachable by other hosts on the same LAN as the node, or by containers running on the same node as the service.
A malicious user could inject commands through the `_data` variable
Magento has a security mitigation bypass vulnerability. Successful exploitation could lead to arbitrary code execution.
Magento has a path traversal vulnerability. Successful exploitation could lead to arbitrary code execution.
LibEtPan has a STARTTLS buffering issue that affects IMAP, SMTP, and POP3. When a server sends a `begin TLS` response, the client reads additional data (e.g., from a meddler-in-the-middle attacker) and evaluates it in a TLS context, aka `response injection.`
In Fiber, the filename that is given in `c.Attachment()` is not escaped, and therefore vulnerable for a CRLF injection attack. An attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc. A possible workaround is to serialize the input before passing it to `ctx.Attachment()`.
Magento has an observable timing discrepancy vulnerability. Successful exploitation could lead to signature verification bypass.
Uvicorn is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.
In TimelineJS, some user data renders as HTML. An attacker could implement an XSS exploit with maliciously crafted content in a number of data fields. This risk is present whether the source data for the timeline is stored on Google Sheets or in a JSON configuration file.
This affects all versions of package UmbracoForms. When using the default configuration for upload forms, it is possible to upload arbitrary file types. The package offers a way for users to mitigate the issue. The users of this package can create a custom workflow and frontend validation that blocks certain file types, depending on their security needs and policies.
Magento has a DOM-based cross-site scripting vulnerability. Successful exploitation could lead to arbitrary code execution.
When a form page type is made available to Wagtail editors through the `wagtail.contrib.forms` app, and the page template is built using Django's standard form rendering helpers such as `form.as_p`, any HTML tags used within a form field's help text will be rendered unescaped in the page. Allowing HTML within help text is an intentional design decision by Django; however, as a matter of policy Wagtail does not allow editors to insert arbitrary HTML by default, as this could potentially be used to carry out cross-site scripting attacks, including privilege escalation.
A buffer overflow in the patching routine of bsdiff4 allows an attacker to write to heap memory (beyond allocated bounds) via a crafted patch file.
In parser-server, an authenticated user using the viewer GraphQL query can bypass all read security on his User object and can also bypass all objects linked via relation or Pointer on his User object.
This affects all versions of package rollup-plugin-dev-server. There is no path sanitization in the `readFile` operation inside the `readFileFromContentBase` function.
An SQL injection vulnerability in `reportdata_controller.php` in the reportdata module for MunkiReport allows attackers to execute arbitrary SQL commands via the `req` parameter of the `/module/reportdata/ip` endpoint.
This affects all versions of the marscode package. There is no path sanitization for the path provided in `fs.readFile` of `index.js`.
A Cross-Site Scripting (XSS) vulnerability in the comment module for MunkiReport allows remote attackers to inject arbitrary web script or HTML by posting a new comment.
The UI in DevSpace allows web-sites to execute actions on pods (on behalf of a victim) because of a lack of authentication for the WebSocket protocol. This leads to remote code execution.
In codecov (npm package), the upload method has a command injection vulnerability. Clients of the codecov-node library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. A similar CVE (CVE-2020-7597 for GHSA-5q88-cjfq-g2mh) was issued but the fix was incomplete. It only blocked `&`, and command injection is still possible using backticks instead to bypass the sanitizer. The attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection.
This affects all versions of package rollup-plugin-server. There is no path sanitization in the `readFile` operation performed inside the `readFileFromContentBase` function.
This affects all versions of the marked-tree package. There is no path sanitization for the path provided in `fs.readFile` of `index.js`.
The automatic permission-checking mechanism in the `silverstripe/graphql` module does not provide complete protection against lists that are limited (e.g., through pagination), resulting in records that should have failed a permission check being added to the final result set. GraphQL endpoints are configured by default (e.g., for assets), but the `admin/graphql` endpoint is access protected by default. This limits the vulnerability to all authenticated users, including those with limited permissions (e.g., where viewing records exposed through `admin/graphql` requires administrator permissions). However, if custom GraphQL endpoints have been configured for a specific implementation (usually under `/graphql`), this vulnerability could also be exploited through unauthenticated requests. This vulnerability only applies to reading records; it does not allow unauthorised changing of records.
Silverstripe CMS can be susceptible to script execution from malicious upload contents under allowed file extensions (for example HTML code in a TXT file). When these files are stored as protected or draft files, the MIME detection can cause browsers to execute the file contents.
MIT Lifelong Kindergarten Scratch scratch-vm loads extension URLs from untrusted `project.json` files with certain `_` characters, resulting in remote code execution because the URL content is treated as a script and is executed as a worker. The responsible code is `getExtensionIdForOpcode` in `serialization/sb3.js`. The use of `_` is incompatible with a protection mechanism in older versions, in which URLs were split and consequently deserialization attacks were prevented.
In SilverStripe, malicious users with a valid Silverstripe CMS login (usually CMS access) can craft profile information which can lead to XSS for other users through specially crafted login form URLs.
Uncontrolled resource consumption in `jpeg-js` allows attacker to launch denial of service attacks using specially a crafted JPEG image.
The Kubernetes kube-apiserver is vulnerable to an unvalidated redirect on proxied upgrade requests that could allow an attacker to escalate privileges from a node compromise to a full cluster compromise.
In openenclave, enclaves that use x87 FPU operations are vulnerable to tampering by a malicious host application. By violating the Linux System V Application Binary Interface (ABI) for such operations, a host app can compromise the execution integrity of some x87 FPU operations in an enclave. Depending on the FPU control configuration of the enclave app and whether the operations are used in secret-dependent execution paths, this vulnerability may also be used to mount a side-channel attack on the enclave.
A Cross-Site Scripting (XSS) vulnerability in the managedinstalls module for MunkiReport allows remote attackers to inject arbitrary web script or HTML via the last two URL parameters (through which installed packages names and versions are reported).
This affects all versions of package fast-http. There is no path sanitization in the path provided at `fs.readFile` in index.js.
Jenkins Matrix Authorization Strategy Plugin does not escape user names shown in the configuration, resulting in a stored cross-site scripting vulnerability.
An SQL injection vulnerability in `softwareupdate_controller.php` in the Software Update module for MunkiReport allows attackers to execute arbitrary SQL commands via the last URL parameter of the `/module/softwareupdate/get_tab_data/` endpoint.
Jenkins Gitlab Authentication Plugin does not perform group authorization checks properly, resulting in a privilege escalation vulnerability.
Prototype pollution attack when using `_.zipObjectDeep` in lodash.
Jenkins Deployer Framework Plugin does not escape the URL displayed in the build home page, resulting in a stored cross-site scripting vulnerability.
In SilverStripe, a specific URL path configured by default through the silverstripe/framework module can be used to disclose the fact that a domain is hosting a Silverstripe application. There is no disclosure of the specific version. The functionality on this URL path is limited to execution in a CLI context, and is not known to present a vulnerability through web-based access. As a side effect, this preconfigured path also blocks the creation of other resources on this path (e.g. a page).
Magento has a stored cross-site scripting vulnerability. Successful exploitation could lead to sensitive information disclosure.
An issue was found in Apache Airflow. When using `CeleryExecutor`, if an attacker can connect to the broker (Redis, RabbitMQ) directly, it is possible to inject commands, resulting in the celery worker running arbitrary commands.
An issue was discovered in `ajv.validate()` in Ajv (aka Another JSON Schema Validator). A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code)
An issue was found in Apache Airflow. When using `CeleryExecutor`, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.
Magento has a php object injection vulnerability. Successful exploitation could lead to arbitrary code execution.
A Path Traversal issue was discovered in the socket.io-file package for Node.js. The `socket.io-file::createFile` message uses path.join with `../` in the name option, and the `uploadDir` and rename options determine the path.
Lua mishandles the interaction between stack resizes and garbage collection, leading to a heap-based buffer overflow, heap-based buffer over-read, or use-after-free.