id stringlengths 13 16 | title stringlengths 0 185 | description stringlengths 35 3.88k | patches listlengths 1 7 | cwe stringclasses 636 values |
|---|---|---|---|---|
CVE-2025-61919 | Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing | Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, `Rack::Request#POST` reads the entire request body into memory for `Content-Type: application/x-www-form-urlencoded`, calling `rack.input.read(nil)` without enforcing a length or cap. Large request bodies can therefore be buffered completely into process memory before parsing, leading to denial of service (DoS) through memory exhaustion. Users should upgrade to Rack version 2.2.20, 3.1.18, or 3.2.3, anu of which enforces form parameter limits using `query_parser.bytesize_limit`, preventing unbounded reads of `application/x-www-form-urlencoded` bodies. Additionally, enforce strict maximum body size at the proxy or web server layer (e.g., Nginx `client_max_body_size`, Apache `LimitRequestBody`). | [
{
"url": "https://github.com/rack/rack/commit/cbd541e8a3d0c5830a3c9a30d3718ce2e124f9db",
"patch_text_b64": "RnJvbSBjYmQ1NDFlOGEzZDBjNTgzMGEzYzlhMzBkMzcxOGNlMmUxMjRmOWRiIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBTYW11ZWwgV2lsbGlhbXMgPHNhbXVlbC53aWxsaWFtc0BvcmlvbnRyYW5zZmVyLmNvLm56PgpEYXRlOiBUaHUsIDkgT2N0IDIw... | CWE-400: Uncontrolled Resource Consumption |
CVE-2025-61780 | Rack has Possible Information Disclosure Vulnerability | Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a "redirect" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely. | [
{
"url": "https://github.com/rack/rack/commit/57277b7741581fa827472c5c666f6e6a33abd784",
"patch_text_b64": "RnJvbSA1NzI3N2I3NzQxNTgxZmE4Mjc0NzJjNWM2NjZmNmU2YTMzYWJkNzg0IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBTYW11ZWwgV2lsbGlhbXMgPHNhbXVlbC53aWxsaWFtc0BvcmlvbnRyYW5zZmVyLmNvLm56PgpEYXRlOiBUdWUsIDcgT2N0IDIw... | CWE-200: Exposure of Sensitive Information to an Unauthorized Actor |
CVE-2024-0217 | Packagekitd: use-after-free in idle function callback | A use-after-free flaw was found in PackageKitd. In some conditions, the order of cleanup mechanics for a transaction could be impacted. As a result, some memory access could occur on memory regions that were previously freed. Once freed, a memory region can be reused for other allocations and any previously stored data in this memory region is considered lost. | [
{
"url": "https://github.com/PackageKit/PackageKit/commit/64278c9127e3333342b56ead99556161f7e86f79",
"patch_text_b64": "RnJvbSA2NDI3OGM5MTI3ZTMzMzMzNDJiNTZlYWQ5OTU1NjE2MWY3ZTg2Zjc5IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBQaGlsaXAgV2l0aG5hbGwgPHB3aXRobmFsbEBlbmRsZXNzb3Mub3JnPgpEYXRlOiBXZWQsIDE1IE1hciAyMDIz... | CWE-416 - Use After Free |
CVE-2023-4385 | Kernel: jfs: null pointer dereference in dbfree() | A NULL pointer dereference flaw was found in dbFree in fs/jfs/jfs_dmap.c in the journaling file system (JFS) in the Linux Kernel. This issue may allow a local attacker to crash the system due to a missing sanity check. | [
{
"url": "https://github.com/torvalds/linux/commit/0d4837fdb796f99369cf7691d33de1b856bcaf1f",
"patch_text_b64": "RnJvbSAwZDQ4MzdmZGI3OTZmOTkzNjljZjc2OTFkMzNkZTFiODU2YmNhZjFmIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBaaXh1YW4gRnUgPHIzM3MzbjZAZ21haWwuY29tPgpEYXRlOiBNb24sIDExIEFwciAyMDIyIDE4OjQ1OjM0ICswODAwClN... | CWE-476 - NULL Pointer Dereference |
CVE-2023-5341 | Imagemagick: heap use-after-free in coders/bmp.c | A heap use-after-free flaw was found in coders/bmp.c in ImageMagick. | [
{
"url": "https://github.com/ImageMagick/ImageMagick/commit/aa673b2e4defc7cad5bec16c4fc8324f71e531f1",
"patch_text_b64": "RnJvbSBhYTY3M2IyZTRkZWZjN2NhZDViZWMxNmM0ZmM4MzI0ZjcxZTUzMWYxIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBDcmlzdHkgPHVyYmFuLXdhcnJpb3JAaW1hZ2VtYWdpY2sub3JnPgpEYXRlOiBTdW4sIDI0IFNlcCAyMDIzID... | CWE-416 - Use After Free |
CVE-2025-8194 | Tarfile infinite loop during parsing with negative member offset | There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously crafted tar archives.
This vulnerability can be mitigated by including the following patch after importing the “tarfile” module: https://gist.github.com/sethmlarson/1716ac5b82b73dbcbf23ad2eff8b33e1 | [
{
"url": "https://github.com/python/cpython/commit/57f5981d6260ed21266e0c26951b8564cc252bc2",
"patch_text_b64": "RnJvbSA1N2Y1OTgxZDYyNjBlZDIxMjY2ZTBjMjY5NTFiODU2NGNjMjUyYmMyIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBWaWN0b3IgU3Rpbm5lciA8dnN0aW5uZXJAcHl0aG9uLm9yZz4KRGF0ZTogVHVlLCAyIFNlcCAyMDI1IDIwOjIwOjI3ICs... | CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop') |
CVE-2025-6069 | HTMLParser quadratic complexity when processing malformed inputs | The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service. | [
{
"url": "https://github.com/python/cpython/commit/fdc9d214c01cb4588f540cfa03726bbf2a33fc15",
"patch_text_b64": "RnJvbSBmZGM5ZDIxNGMwMWNiNDU4OGY1NDBjZmEwMzcyNmJiZjJhMzNmYzE1IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBTZXJoaXkgU3RvcmNoYWthIDxzdG9yY2hha2FAZ21haWwuY29tPgpEYXRlOiBGcmksIDQgSnVsIDIwMjUgMDA6MDU6NTM... | CWE-1333 Inefficient Regular Expression Complexity |
CVE-2025-61787 | Deno is Vulnerable to Command Injection on Windows During Batch File Execution | Deno is a JavaScript, TypeScript, and WebAssembly runtime. Versions prior to 2.5.3 and 2.2.15 are vulnerable to Command Line Injection attacks on Windows when batch files are executed. In Windows, ``CreateProcess()`` always implicitly spawns ``cmd.exe`` if a batch file (.bat, .cmd, etc.) is being executed even if the application does not specify it via the command line. This makes Deno vulnerable to a command injection attack on Windows. Versions 2.5.3 and 2.2.15 fix the issue. | [
{
"url": "https://github.com/denoland/deno/commit/8a0990ccd37bafd8768176ca64b906ba2da2d822",
"patch_text_b64": "RnJvbSA4YTA5OTBjY2QzN2JhZmQ4NzY4MTc2Y2E2NGI5MDZiYTJkYTJkODIyIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBEaXZ5IDxkai5zcml2YXN0YXZhMjNAZ21haWwuY29tPgpEYXRlOiBXZWQsIDI0IFNlcCAyMDI1IDEwOjM1OjM3ICswNTMw... | CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') |
CVE-2025-61788 | Opencast Paella Player 7 vulnerable to Cross-Site-Scripting | Opencast is a free, open-source platform to support the management of educational audio and video content. Prior to Opencast 17.8 and 18.2, the paella would include and render some user inputs (metadata like title, description, etc.) unfiltered and unmodified. The vulnerability allows attackers to inject and malicious HTML and JavaScript in the player, which would then be executed in the browsers of users watching the prepared media. This can then be used to modify the site or to execute actions in the name of logged-in users. To inject malicious metadata, an attacker needs write access to the system. For example, the ability to upload media and modify metadata. This cannot be exploited by unauthenticated users. This issue is fixed in Opencast 17.8 and 18.2. | [
{
"url": "https://github.com/opencast/opencast/commit/2809520fa88d108d8104c760f00c10bad42c14f9",
"patch_text_b64": "RnJvbSBhYTcwZTRhMTczNGVlYTJlOWJjZWFlNTJlOTJmMDBhNTQwMmE0M2FiIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBNaWd1ZWwgRXNjcml2YSA8bWllc2dyZUBnbWFpbC5jb20+CkRhdGU6IFdlZCwgMTcgU2VwIDIwMjUgMTE6NTY6MTkg... | CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') |
CVE-2024-11831 | Npm-serialize-javascript: cross-site scripting (xss) in serialize-javascript | A flaw was found in npm-serialize-javascript. The vulnerability occurs because the serialize-javascript module does not properly sanitize certain inputs, such as regex or other JavaScript object types, allowing an attacker to inject malicious code. This code could be executed when deserialized by a web browser, causing Cross-site scripting (XSS) attacks. This issue is critical in environments where serialized data is sent to web clients, potentially compromising the security of the website or web application using this package. | [
{
"url": "https://github.com/yahoo/serialize-javascript/commit/f27d65d3de42affe2aac14607066c293891cec4e",
"patch_text_b64": "RnJvbSBmMjdkNjVkM2RlNDJhZmZlMmFhYzE0NjA3MDY2YzI5Mzg5MWNlYzRlIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBSeWFuIERlbGFuZXkgPHJ5YW5AcmV2ZXJlY3JlLmNvbT4KRGF0ZTogTW9uLCA4IEphbiAyMDI0IDE3OjA... | CWE-79 - Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') |
CVE-2025-61672 | Synapse: Invalid device keys degrade federation functionality | Synapse is an open source Matrix homeserver implementation. Lack of validation for device keys in Synapse before 1.138.3 and in Synapse 1.139.0 allow an attacker registered on the victim homeserver to degrade federation functionality, unpredictably breaking outbound federation to other homeservers. The issue is patched in Synapse 1.138.3, 1.138.4, 1.139.1, and 1.139.2. Note that even though 1.138.3 and 1.139.1 fix the vulnerability, they inadvertently introduced an unrelated regression. For this reason, the maintainers of Synapse recommend skipping these releases and upgrading straight to 1.138.4 and 1.139.2. | [
{
"url": "https://github.com/element-hq/synapse/commit/26aaaf9e48fff80cf67a20c691c75d670034b3c1",
"patch_text_b64": "RnJvbSAyNmFhYWY5ZTQ4ZmZmODBjZjY3YTIwYzY5MWM3NWQ2NzAwMzRiM2MxIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBUaWxsIDwyMzUzMTAwK1M3ZXZpbktAdXNlcnMubm9yZXBseS5naXRodWIuY29tPgpEYXRlOiBUdWUsIDcgT2N0IDI... | CWE-1287: Improper Validation of Specified Type of Input |
CVE-2024-8088 | Infinite loop when iterating over zip archive entry names from zipfile.Path | There is a HIGH severity vulnerability affecting the CPython "zipfile"
module affecting "zipfile.Path". Note that the more common API "zipfile.ZipFile" class is unaffected.
When iterating over names of entries in a zip archive (for example, methods
of "zipfile.Path" like "namelist()", "iterdir()", etc)
the process can be put into an infinite loop with a maliciously crafted
zip archive. This defect applies when reading only metadata or extracting
the contents of the zip archive. Programs that are not handling
user-controlled zip archives are not affected. | [
{
"url": "https://github.com/python/cpython/commit/7bc367e464ce50b956dd232c1dfa1cad4e7fb814",
"patch_text_b64": "RnJvbSA3YmMzNjdlNDY0Y2U1MGI5NTZkZDIzMmMxZGZhMWNhZDRlN2ZiODE0IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiAiSmFzb24gUi4gQ29vbWJzIiA8amFyYWNvQGphcmFjby5jb20+CkRhdGU6IFdlZCwgNCBTZXAgMjAyNCAxMTo0MDo1NiA... | CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop') |
CVE-2025-61771 | Rack's multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion) | Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, ``Rack::Multipart::Parser` stores non-file form fields (parts without a `filename`) entirely in memory as Ruby `String` objects. A single large text field in a multipart/form-data request (hundreds of megabytes or more) can consume equivalent process memory, potentially leading to out-of-memory (OOM) conditions and denial of service (DoS). Attackers can send large non-file fields to trigger excessive memory usage. Impact scales with request size and concurrency, potentially leading to worker crashes or severe garbage-collection overhead. All Rack applications processing multipart form submissions are affected. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a reasonable size cap for non-file fields (e.g., 2 MiB). Workarounds include restricting maximum request body size at the web-server or proxy layer (e.g., Nginx `client_max_body_size`) and validating and rejecting unusually large form fields at the application level. | [
{
"url": "https://github.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181e",
"patch_text_b64": "RnJvbSA1ODkxMjdmNGFjOGI1Y2YxMWNmODhmYjBjZDExNmZmZWQ0ZDIxODFlIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBKZXJlbXkgRXZhbnMgPGNvZGVAamVyZW15ZXZhbnMubmV0PgpEYXRlOiBNb24sIDE1IFNlcCAyMDI1IDE3OjE3OjAzIC0wNzAw... | CWE-400: Uncontrolled Resource Consumption |
CVE-2025-61772 | Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion) | Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, `Rack::Multipart::Parser` can accumulate unbounded data when a multipart part’s header block never terminates with the required blank line (`CRLFCRLF`). The parser keeps appending incoming bytes to memory without a size cap, allowing a remote attacker to exhaust memory and cause a denial of service (DoS). Attackers can send incomplete multipart headers to trigger high memory use, leading to process termination (OOM) or severe slowdown. The effect scales with request size limits and concurrency. All applications handling multipart uploads may be affected. Versions 2.2.19, 3.1.17, and 3.2.2 cap per-part header size (e.g., 64 KiB). As a workaround, restrict maximum request sizes at the proxy or web server layer (e.g., Nginx `client_max_body_size`). | [
{
"url": "https://github.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181e",
"patch_text_b64": "RnJvbSA1ODkxMjdmNGFjOGI1Y2YxMWNmODhmYjBjZDExNmZmZWQ0ZDIxODFlIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBKZXJlbXkgRXZhbnMgPGNvZGVAamVyZW15ZXZhbnMubmV0PgpEYXRlOiBNb24sIDE1IFNlcCAyMDI1IDE3OjE3OjAzIC0wNzAw... | CWE-400: Uncontrolled Resource Consumption |
CVE-2025-61770 | Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion) | Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, `Rack::Multipart::Parser` buffers the entire multipart preamble (bytes before the first boundary) in memory without any size limit. A client can send a large preamble followed by a valid boundary, causing significant memory use and potential process termination due to out-of-memory (OOM) conditions. Remote attackers can trigger large transient memory spikes by including a long preamble in multipart/form-data requests. The impact scales with allowed request sizes and concurrency, potentially causing worker crashes or severe slowdown due to garbage collection. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a preamble size limit (e.g., 16 KiB) or discard preamble data entirely. Workarounds include limiting total request body size at the proxy or web server level and monitoring memory and set per-process limits to prevent OOM conditions. | [
{
"url": "https://github.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181e",
"patch_text_b64": "RnJvbSA1ODkxMjdmNGFjOGI1Y2YxMWNmODhmYjBjZDExNmZmZWQ0ZDIxODFlIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBKZXJlbXkgRXZhbnMgPGNvZGVAamVyZW15ZXZhbnMubmV0PgpEYXRlOiBNb24sIDE1IFNlcCAyMDI1IDE3OjE3OjAzIC0wNzAw... | CWE-400: Uncontrolled Resource Consumption |
CVE-2025-61962 | In fetchmail before 6.5.6, the SMTP client can crash when authenticating upon receiving a 334 status code in a malformed context. | [
{
"url": "https://gitlab.com/fetchmail/fetchmail/-/commit/4c3cebfa4e659fb778ca2cae0ccb3f69201609a8",
"patch_text_b64": "RnJvbSA0YzNjZWJmYTRlNjU5ZmI3NzhjYTJjYWUwY2NiM2Y2OTIwMTYwOWE4IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBNYXR0aGlhcyBBbmRyZWUgPG1hdHRoaWFzLmFuZHJlZUBnbXguZGU+CkRhdGU6IEZyaSwgMyBPY3QgMjAyNSAx... | CWE-142 Improper Neutralization of Value Delimiters | |
CVE-2025-3193 | Versions of the package algoliasearch-helper from 2.0.0-rc1 and before 3.11.2 are vulnerable to Prototype Pollution in the _merge() function in merge.js, which allows constructor.prototype to be written even though doing so throws an error. In the "extreme edge-case" that the resulting error is caught, code injected into the user-supplied search parameter may be exeucted.
This is related to but distinct from the issue reported in [CVE-2021-23433](https://security.snyk.io/vuln/SNYK-JS-ALGOLIASEARCHHELPER-1570421).
**NOTE:** This vulnerability is not exploitable in the default configuration of InstantSearch since searchParameters are not modifiable by users. | [
{
"url": "https://github.com/algolia/algoliasearch-helper-js/commit/776dff23c87b0902e554e02a8c2567d2580fe12a",
"patch_text_b64": "RnJvbSA3NzZkZmYyM2M4N2IwOTAyZTU1NGUwMmE4YzI1NjdkMjU4MGZlMTJhIE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBIYXJvZW4gVmlhZW5lIDxoZWxsb0BoYXJvZW4ubWU+CkRhdGU6IE1vbiwgOSBKYW4gMjAyMyAxMD... | CWE-1321 - Prototype Pollution | |
CVE-2025-61606 | WeGIA: Open Redirect Vulnerability in `control.php` endpoint | WeGIA is an open source web manager with a focus on charitable institutions. Versions 3.4.12 and below contain an Open Redirect vulnerability, identified in the control.php endpoint, specifically in the nextPage parameter (metodo=listarUmnomeClasse=FuncionarioControle). This vulnerability allows attackers to redirect users to arbitrary external domains, enabling phishing campaigns, malicious payload distribution, or user credential theft. This issue is fixed in version 3.5.0. | [
{
"url": "https://github.com/LabRedesCefetRJ/WeGIA/commit/85051ad14b1e7fa14116e74a90c0bd5480b2ec84",
"patch_text_b64": "RnJvbSA4NTA1MWFkMTRiMWU3ZmExNDExNmU3NGE5MGMwYmQ1NDgwYjJlYzg0IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBHYWJyaWVsUGludG9Tb3V6YSA8Z2FicmllbHBpbnRvc291ejRAZ21haWwuY29tPgpEYXRlOiBUaHUsIDExIFNl... | CWE-601: URL Redirection to Untrusted Site ('Open Redirect') |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 13