Common Weakness Enumeration

CWE-400

Discouraged

Uncontrolled Resource Consumption

Abstraction: Class · Status: Draft

API response cwe.mitre.org

The product does not properly control the allocation and maintenance of a limited resource.

5423 vulnerabilities reference this CWE, most recent first.

GHSA-HCQ4-PVMG-M2GP

Vulnerability from github – Published: 2024-06-01 18:30 – Updated: 2025-01-30 15:31
VLAI
Details

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the lunary-ai/lunary application, version 1.2.10. An attacker can exploit this vulnerability by maliciously manipulating regular expressions, which can significantly impact the response time of the application and potentially render it completely non-functional. Specifically, the vulnerability can be triggered by sending a specially crafted request to the application, leading to a denial of service where the application crashes.

Severity
7.5 (High)
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2024-4148"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-1333",
      "CWE-400"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-06-01T16:15:07Z",
    "severity": "HIGH"
  },
  "details": "A Regular Expression Denial of Service (ReDoS) vulnerability exists in the lunary-ai/lunary application, version 1.2.10. An attacker can exploit this vulnerability by maliciously manipulating regular expressions, which can significantly impact the response time of the application and potentially render it completely non-functional. Specifically, the vulnerability can be triggered by sending a specially crafted request to the application, leading to a denial of service where the application crashes.",
  "id": "GHSA-hcq4-pvmg-m2gp",
  "modified": "2025-01-30T15:31:36Z",
  "published": "2024-06-01T18:30:46Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-4148"
    },
    {
      "type": "WEB",
      "url": "https://github.com/lunary-ai/lunary/commit/1e8a3d941ba5cfef2c478dd5bac4e4a4b4d67830"
    },
    {
      "type": "WEB",
      "url": "https://huntr.com/bounties/eca4ad45-2a38-4f3c-9ec1-8205cd51be31"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-HCW2-VPP7-52V9

Vulnerability from github – Published: 2026-05-28 21:32 – Updated: 2026-05-28 21:32
VLAI
Details

Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated low-privileged user can cause Kibana to consume exponentially increasing amounts of memory by submitting a specially crafted Timelion visualization expression containing deeply chained function calls. The resulting data structure grows without bound, exhausting available memory and causing the Kibana service to crash and become unavailable to all users.

Severity
6.5 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-42399"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-28T21:16:30Z",
    "severity": "MODERATE"
  },
  "details": "Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated low-privileged user can cause Kibana to consume exponentially increasing amounts of memory by submitting a specially crafted Timelion visualization expression containing deeply chained function calls. The resulting data structure grows without bound, exhausting available memory and causing the Kibana service to crash and become unavailable to all users.",
  "id": "GHSA-hcw2-vpp7-52v9",
  "modified": "2026-05-28T21:32:05Z",
  "published": "2026-05-28T21:32:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42399"
    },
    {
      "type": "WEB",
      "url": "https://discuss.elastic.co/t/kibana-8-19-16-and-9-3-5-security-update-esa-2026-36/386556"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-HF25-HWQC-V6G2

Vulnerability from github – Published: 2023-05-16 00:30 – Updated: 2024-04-04 04:11
VLAI
Details

In pushDynamicShortcut of ShortcutPackage.java, there is a possible way to get the device into a boot loop due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-250576066

Severity
5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2023-20930"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400",
      "CWE-770"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-05-15T22:15:11Z",
    "severity": "MODERATE"
  },
  "details": "In pushDynamicShortcut of ShortcutPackage.java, there is a possible way to get the device into a boot loop due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-250576066",
  "id": "GHSA-hf25-hwqc-v6g2",
  "modified": "2024-04-04T04:11:24Z",
  "published": "2023-05-16T00:30:17Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-20930"
    },
    {
      "type": "WEB",
      "url": "https://source.android.com/security/bulletin/2023-05-01"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-HF2F-3FP9-M472

Vulnerability from github – Published: 2023-08-02 00:30 – Updated: 2024-04-04 06:29
VLAI
Details

An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.14 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. A Regular Expression Denial of Service was possible via sending crafted payloads which use AutolinkFilter to the preview_markdown endpoint.

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2023-3364"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-1333",
      "CWE-400"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-08-02T00:15:18Z",
    "severity": "HIGH"
  },
  "details": "An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.14 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. A Regular Expression Denial of Service was possible via sending crafted payloads which use AutolinkFilter to the preview_markdown endpoint.",
  "id": "GHSA-hf2f-3fp9-m472",
  "modified": "2024-04-04T06:29:16Z",
  "published": "2023-08-02T00:30:40Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3364"
    },
    {
      "type": "WEB",
      "url": "https://hackerone.com/reports/1959727"
    },
    {
      "type": "WEB",
      "url": "https://gitlab.com/gitlab-org/gitlab/-/issues/415995"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-HF2G-6J7H-98WG

Vulnerability from github – Published: 2026-06-05 16:41 – Updated: 2026-06-09 18:40
VLAI
Summary
klever-go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS
Details

Summary

networkMessenger.directMessageHandler in network/p2p/libp2p/netMessenger.go spawns a fresh goroutine for every incoming direct message before the antiflood layer makes an admission decision. There is no semaphore, throttler, or bound on concurrent in-flight spawns.

A single connected libp2p peer can open a DirectSendID stream and send well-formed TopicMessage envelopes with varying sequence numbers. Each accepted direct message reaches directMessageHandler and triggers a fresh goroutine before processor.ProcessReceivedMessage runs. This allows unbounded goroutine growth and node availability degradation from one peer.

This remains present in the latest release v1.7.17: network/p2p/libp2p/netMessenger.go:1060 still spawns go func(msg p2p.MessageP2P) before processor.ProcessReceivedMessage. I also verified current develop commit 10bcfd50, where the same spawn remains at network/p2p/libp2p/netMessenger.go:1115.

This is distinct from GHSA-74m6-4hjp-7226 and GHSA-87m7-qffr-542v. Those advisories concern MultiDataInterceptor decompression/throttler behavior. This report concerns the libp2p direct-message ingress wrapper spawning an unbounded goroutine before processor-level antiflood/admission logic runs. A patch to Batch.Decompress or MultiDataInterceptor does not bound this direct-message goroutine spawn.

Details

The affected path is network/p2p/libp2p/netMessenger.go in directMessageHandler.

The direct-message path transforms and validates the message, looks up the topic processor, then immediately spawns a goroutine:

func (netMes *networkMessenger) directMessageHandler(message *pubsub.Message, fromConnectedPeer core.PeerID) error {
    var processor p2p.MessageProcessor

    topic := *message.Topic
    msg, err := netMes.transformAndCheckMessage(message, fromConnectedPeer, topic)
    if err != nil {
        return err
    }

    netMes.mutTopics.RLock()
    processor = netMes.processors[topic]
    netMes.mutTopics.RUnlock()

    if processor == nil {
        return fmt.Errorf("%w on directMessageHandler for topic %s", p2p.ErrNilValidator, topic)
    }

    go func(msg p2p.MessageP2P) {
        if check.IfNil(msg) {
            return
        }

        errProcess := processor.ProcessReceivedMessage(msg, fromConnectedPeer)
        // ...
    }(msg)

    return nil
}

The processor-level antiflood decision happens inside ProcessReceivedMessage, after the goroutine, its stack, and the cloned message reference already exist. That means antiflood can bound processing rate, but not goroutine creation rate.

The existing goRoutinesThrottler with capacity broadcastGoRoutines = 1000 is wired into outgoing broadcast paths such as BroadcastOnChannelBlocking, not this incoming direct-message path.

The parallel pubsub ingress path in the same file handles a comparable inbound message surface synchronously:

err = handler.ProcessReceivedMessage(msg, fromConnectedPeer)

So the direct-message path is asymmetric: same transform/check function, same ProcessReceivedMessage callee, but direct-message ingress adds an unbounded goroutine spawn.

Reachability:

  • directSender.go registers DirectSendID as a libp2p stream protocol.
  • directStreamHandler reads framed pubsub.Message envelopes from the stream.
  • directStreamHandler forwards each message to networkMessenger.directMessageHandler.
  • Any connected peer can send well-formed envelopes to registered topics.
  • The seenMessages cache keys on From + Seqno; Seqno is attacker-controlled in the envelope, so incrementing it bypasses dedupe.

PoC

GitHub Private Vulnerability Reporting does not appear to allow file attachments in this form, so I am including the reproduction command and captured output inline. I can provide the full Go test file immediately if useful.

The PoC is a Go test file intended to be placed under network/p2p/libp2p/ in a klever-go checkout. It exercises the real network/p2p/libp2p package with NewMockMessenger.

Reproduction:

git clone https://github.com/klever-io/klever-go
cd klever-go
git checkout v1.7.16

# Place dos_directmsg_test.go into:
# network/p2p/libp2p/

go test ./network/p2p/libp2p/ -run TestPoC_ -count=1 -v -timeout 60s

Captured output:

=== RUN   TestPoC_DirectMessageHandler_SpawnsGoroutinePerMessage
    baseline goroutines: 43
    peak goroutines after 500 direct messages: 543 (delta = 500)
    final goroutines after drain + GC: 43
POC_RESULT direct=spawn N=500 baseline=43 peak=543 delta=500 threshold=400 final=43
--- PASS

=== RUN   TestPoC_SynchronousHandler_NoGoroutineGrowth
    baseline goroutines: 47
    peak goroutines after 500 synchronous calls: 47 (delta = 0)
POC_RESULT sync=block N=500 baseline=47 peak=47 delta=0
--- PASS

=== RUN   TestPoC_DirectMessageHandler_NoThrottlerInPath
    all 2000 SendToConnectedPeer calls returned in 2.490708ms -- no throttler blocking
POC_RESULT throttler=absent N=2000 elapsed=2.490708ms
--- PASS

Reading:

  1. 500 direct messages with slow processors produced exactly 500 new goroutines.
  2. The synchronous control path produced zero goroutine growth.
  3. 2000 messages, twice the outgoing broadcastGoRoutines = 1000 capacity, returned immediately, showing no ingress throttler blocks this path.

Impact

A single connected peer can sustain unbounded goroutine spawn growth on a klever-go node. Each spawned goroutine allocates its own stack, holds message references until the processor returns, and adds scheduler and GC pressure before antiflood admission can reject the message.

Under realistic attacker line rate and non-trivial processor latency, goroutine count can grow faster than the runtime drains it, degrading the node's ability to process legitimate traffic. This maps to the SECURITY.md High category: "Denial of Service affecting network availability."

All testing was local only. I did not contact Klever mainnet, public testnet, hosted RPCs, explorers, or third-party production infrastructure.

Suggested fixes:

  1. Wire goRoutinesThrottler.CanProcess() or a dedicated ingress throttler before the go func() spawn in directMessageHandler.
  2. Or remove the goroutine and call ProcessReceivedMessage synchronously, matching the existing pubsubCallback path.

Disclosure note: I originally sent this report to security@klever.org on 2026-05-13. Since SECURITY.md lists GitHub Private Vulnerability Reporting as the recommended channel, I am resubmitting it here.

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.7.17"
      },
      "package": {
        "ecosystem": "Go",
        "name": "github.com/klever-io/klever-go"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.7.14"
            },
            {
              "fixed": "1.7.18"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-52879"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400",
      "CWE-770"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-05T16:41:23Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Summary\n\n`networkMessenger.directMessageHandler` in `network/p2p/libp2p/netMessenger.go` spawns a fresh goroutine for every incoming direct message before the antiflood layer makes an admission decision. There is no semaphore, throttler, or bound on concurrent in-flight spawns.\n\nA single connected libp2p peer can open a `DirectSendID` stream and send well-formed `TopicMessage` envelopes with varying sequence numbers. Each accepted direct message reaches `directMessageHandler` and triggers a fresh goroutine before `processor.ProcessReceivedMessage` runs. This allows unbounded goroutine growth and node availability degradation from one peer.\n\nThis remains present in the latest release `v1.7.17`: `network/p2p/libp2p/netMessenger.go:1060` still spawns `go func(msg p2p.MessageP2P)` before `processor.ProcessReceivedMessage`. I also verified current `develop` commit `10bcfd50`, where the same spawn remains at `network/p2p/libp2p/netMessenger.go:1115`.\n\nThis is distinct from GHSA-74m6-4hjp-7226 and GHSA-87m7-qffr-542v. Those advisories concern `MultiDataInterceptor` decompression/throttler behavior. This report concerns the libp2p direct-message ingress wrapper spawning an unbounded goroutine before processor-level antiflood/admission logic runs. A patch to `Batch.Decompress` or `MultiDataInterceptor` does not bound this direct-message goroutine spawn.\n\n### Details\n\nThe affected path is `network/p2p/libp2p/netMessenger.go` in `directMessageHandler`.\n\nThe direct-message path transforms and validates the message, looks up the topic processor, then immediately spawns a goroutine:\n\n```go\nfunc (netMes *networkMessenger) directMessageHandler(message *pubsub.Message, fromConnectedPeer core.PeerID) error {\n    var processor p2p.MessageProcessor\n\n    topic := *message.Topic\n    msg, err := netMes.transformAndCheckMessage(message, fromConnectedPeer, topic)\n    if err != nil {\n        return err\n    }\n\n    netMes.mutTopics.RLock()\n    processor = netMes.processors[topic]\n    netMes.mutTopics.RUnlock()\n\n    if processor == nil {\n        return fmt.Errorf(\"%w on directMessageHandler for topic %s\", p2p.ErrNilValidator, topic)\n    }\n\n    go func(msg p2p.MessageP2P) {\n        if check.IfNil(msg) {\n            return\n        }\n\n        errProcess := processor.ProcessReceivedMessage(msg, fromConnectedPeer)\n        // ...\n    }(msg)\n\n    return nil\n}\n```\n\nThe processor-level antiflood decision happens inside `ProcessReceivedMessage`, after the goroutine, its stack, and the cloned message reference already exist. That means antiflood can bound processing rate, but not goroutine creation rate.\n\nThe existing `goRoutinesThrottler` with capacity `broadcastGoRoutines = 1000` is wired into outgoing broadcast paths such as `BroadcastOnChannelBlocking`, not this incoming direct-message path.\n\nThe parallel pubsub ingress path in the same file handles a comparable inbound message surface synchronously:\n\n```go\nerr = handler.ProcessReceivedMessage(msg, fromConnectedPeer)\n```\n\nSo the direct-message path is asymmetric: same transform/check function, same `ProcessReceivedMessage` callee, but direct-message ingress adds an unbounded goroutine spawn.\n\nReachability:\n\n- `directSender.go` registers `DirectSendID` as a libp2p stream protocol.\n- `directStreamHandler` reads framed `pubsub.Message` envelopes from the stream.\n- `directStreamHandler` forwards each message to `networkMessenger.directMessageHandler`.\n- Any connected peer can send well-formed envelopes to registered topics.\n- The `seenMessages` cache keys on `From + Seqno`; `Seqno` is attacker-controlled in the envelope, so incrementing it bypasses dedupe.\n\n### PoC\n\nGitHub Private Vulnerability Reporting does not appear to allow file attachments in this form, so I am including the reproduction command and captured output inline. I can provide the full Go test file immediately if useful.\n\nThe PoC is a Go test file intended to be placed under `network/p2p/libp2p/` in a `klever-go` checkout. It exercises the real `network/p2p/libp2p` package with `NewMockMessenger`.\n\nReproduction:\n\n```bash\ngit clone https://github.com/klever-io/klever-go\ncd klever-go\ngit checkout v1.7.16\n\n# Place dos_directmsg_test.go into:\n# network/p2p/libp2p/\n\ngo test ./network/p2p/libp2p/ -run TestPoC_ -count=1 -v -timeout 60s\n```\n\nCaptured output:\n\n```text\n=== RUN   TestPoC_DirectMessageHandler_SpawnsGoroutinePerMessage\n    baseline goroutines: 43\n    peak goroutines after 500 direct messages: 543 (delta = 500)\n    final goroutines after drain + GC: 43\nPOC_RESULT direct=spawn N=500 baseline=43 peak=543 delta=500 threshold=400 final=43\n--- PASS\n\n=== RUN   TestPoC_SynchronousHandler_NoGoroutineGrowth\n    baseline goroutines: 47\n    peak goroutines after 500 synchronous calls: 47 (delta = 0)\nPOC_RESULT sync=block N=500 baseline=47 peak=47 delta=0\n--- PASS\n\n=== RUN   TestPoC_DirectMessageHandler_NoThrottlerInPath\n    all 2000 SendToConnectedPeer calls returned in 2.490708ms -- no throttler blocking\nPOC_RESULT throttler=absent N=2000 elapsed=2.490708ms\n--- PASS\n```\n\nReading:\n\n1. 500 direct messages with slow processors produced exactly 500 new goroutines.\n2. The synchronous control path produced zero goroutine growth.\n3. 2000 messages, twice the outgoing `broadcastGoRoutines = 1000` capacity, returned immediately, showing no ingress throttler blocks this path.\n\n### Impact\n\nA single connected peer can sustain unbounded goroutine spawn growth on a klever-go node. Each spawned goroutine allocates its own stack, holds message references until the processor returns, and adds scheduler and GC pressure before antiflood admission can reject the message.\n\nUnder realistic attacker line rate and non-trivial processor latency, goroutine count can grow faster than the runtime drains it, degrading the node\u0027s ability to process legitimate traffic. This maps to the `SECURITY.md` High category: \"Denial of Service affecting network availability.\"\n\nAll testing was local only. I did not contact Klever mainnet, public testnet, hosted RPCs, explorers, or third-party production infrastructure.\n\nSuggested fixes:\n\n1. Wire `goRoutinesThrottler.CanProcess()` or a dedicated ingress throttler before the `go func()` spawn in `directMessageHandler`.\n2. Or remove the goroutine and call `ProcessReceivedMessage` synchronously, matching the existing `pubsubCallback` path.\n\nDisclosure note: I originally sent this report to `security@klever.org` on 2026-05-13. Since `SECURITY.md` lists GitHub Private Vulnerability Reporting as the recommended channel, I am resubmitting it here.",
  "id": "GHSA-hf2g-6j7h-98wg",
  "modified": "2026-06-09T18:40:40Z",
  "published": "2026-06-05T16:41:23Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/klever-io/klever-go/security/advisories/GHSA-hf2g-6j7h-98wg"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/klever-io/klever-go"
    },
    {
      "type": "WEB",
      "url": "https://github.com/klever-io/klever-go/releases/tag/v1.7.18"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "klever-go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS"
}

GHSA-HF3P-GPVX-Q597

Vulnerability from github – Published: 2025-05-22 15:34 – Updated: 2025-08-12 12:30
VLAI
Details

A flaw was found in gnome-remote-desktop. Once gnome-remote-desktop listens for RDP connections, an unauthenticated attacker can exhaust system resources and repeatedly crash the process. There may be a resource leak after many attacks, which will also result in gnome-remote-desktop no longer being able to open files even after it is restarted via systemd.

Severity
7.4 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-5024"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-05-22T15:16:05Z",
    "severity": "HIGH"
  },
  "details": "A flaw was found in gnome-remote-desktop. Once gnome-remote-desktop listens for RDP connections, an unauthenticated attacker can exhaust system resources and repeatedly crash the process. There may be a resource leak after many attacks, which will also result in gnome-remote-desktop no longer being able to open files even after it is restarted via systemd.",
  "id": "GHSA-hf3p-gpvx-q597",
  "modified": "2025-08-12T12:30:32Z",
  "published": "2025-05-22T15:34:51Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-5024"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:10631"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:10635"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:10742"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:11403"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:11404"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:11405"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:11406"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:11407"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:11408"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2025:11418"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/security/cve/CVE-2025-5024"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2367717"
    },
    {
      "type": "WEB",
      "url": "https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/321"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-HF44-3MX6-VHHW

Vulnerability from github – Published: 2021-05-19 23:02 – Updated: 2021-05-19 19:49
VLAI
Summary
Navigate endpoint is vulnerable to regex injection that may lead to Denial of Service.
Details

Impact

The regex injection that may lead to Denial of Service.

Patches

Will be patched in 2.4 and 3.0

Workarounds

Versions lower than 2.x are only affected if the navigation module is added

References

See this pull request for the fix: https://github.com/graphhopper/graphhopper/pull/2304

If you have any questions or comments about this advisory please send us an Email or create a topic here.

Severity
6.5 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "com.graphhopper:graphhopper-nav"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2021-29506"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2021-05-19T19:49:11Z",
    "nvd_published_at": "2021-05-13T19:15:00Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nThe regex injection that may lead to Denial of Service.\n\n### Patches\nWill be patched in 2.4 and 3.0\n\n### Workarounds\nVersions lower than 2.x are only affected if the navigation module is added\n\n### References\nSee this pull request for the fix: https://github.com/graphhopper/graphhopper/pull/2304\n\nIf you have any questions or comments about this advisory please [send us an Email](https://www.graphhopper.com/contact-form/) or create a topic [here](https://discuss.graphhopper.com/).",
  "id": "GHSA-hf44-3mx6-vhhw",
  "modified": "2021-05-19T19:49:11Z",
  "published": "2021-05-19T23:02:57Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/graphhopper/graphhopper/security/advisories/GHSA-hf44-3mx6-vhhw"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-29506"
    },
    {
      "type": "WEB",
      "url": "https://github.com/graphhopper/graphhopper/pull/2304"
    },
    {
      "type": "WEB",
      "url": "https://github.com/graphhopper/graphhopper/commit/eb189be1fa7443ebf4ae881e737a18f818c95f41"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Navigate endpoint is vulnerable to regex injection that may lead to Denial of Service."
}

GHSA-HF5H-HH56-3VRG

Vulnerability from github – Published: 2020-09-01 16:02 – Updated: 2020-08-31 18:12
VLAI
Summary
Denial of Service in uws
Details

Affected versions of uws do not properly handle large websocket messages when permessage-deflate is enabled, which may result in a denial of service condition.

If uws recieves a 256Mb websocket message when permessage-deflate is enabled, the server will compress the message prior to executing the length check, and subsequently extract the message prior to processing. This can result in a situation where an excessively large websocket message passes the length checks, yet still gets cast from a Buffer to a string, which will exceed v8's maximum string size and crash the process.

Recommendation

Update to version 0.10.9 or later.

Alternatively, disable permessage-deflate.

Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.10.8"
      },
      "package": {
        "ecosystem": "npm",
        "name": "uws"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.10.0"
            },
            {
              "fixed": "0.10.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2016-10544"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-08-31T18:12:32Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "Affected versions of `uws` do not properly handle large websocket messages when `permessage-deflate` is enabled, which may result in a denial of service condition.\n\nIf `uws` recieves a 256Mb websocket message when `permessage-deflate` is enabled, the server will compress the message prior to executing the length check, and subsequently extract the message prior to processing. This can result in a situation where an excessively large websocket message passes the length checks, yet still gets cast from a Buffer to a string, which will exceed v8\u0027s maximum string size and crash the process.\n\n\n## Recommendation\n\nUpdate to version 0.10.9 or later.\n\nAlternatively, disable `permessage-deflate`.",
  "id": "GHSA-hf5h-hh56-3vrg",
  "modified": "2020-08-31T18:12:32Z",
  "published": "2020-09-01T16:02:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2016-10544"
    },
    {
      "type": "WEB",
      "url": "https://github.com/uWebSockets/uWebSockets/commit/37deefd01f0875e133ea967122e3a5e421b8fcd9"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/149"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Denial of Service in uws"
}

GHSA-HF6X-8P5F-CGMF

Vulnerability from github – Published: 2026-07-01 18:31 – Updated: 2026-07-01 18:31
VLAI
Details

Uncontrolled Resource Consumption vulnerability in the HTTP/1.1 message parser in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows an remote attacker to cause a denial of service through memory exhaustion by sending messages with excessive number of headers / excessive header length

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-54399"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-01T17:16:36Z",
    "severity": "HIGH"
  },
  "details": "Uncontrolled Resource Consumption vulnerability in the HTTP/1.1 message parser\u00a0in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows\u00a0an remote attacker to cause a denial of service through memory exhaustion by sending messages with excessive number of headers / excessive header length",
  "id": "GHSA-hf6x-8p5f-cgmf",
  "modified": "2026-07-01T18:31:55Z",
  "published": "2026-07-01T18:31:55Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54399"
    },
    {
      "type": "WEB",
      "url": "https://lists.apache.org/thread/zmxh1pl2zohov5ntdh4lt85gfrlchgpy"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2026/07/01/4"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-HFG7-J82C-FR3W

Vulnerability from github – Published: 2024-05-24 20:09 – Updated: 2024-08-22 21:40
VLAI
Summary
Soot Infinite Loop vulnerability
Details

An infinite loop in the retrieveActiveBody function of Soot before v4.4.1 under Java 8 allows attackers to cause a Denial of Service (DoS).

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.soot-oss:soot"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.4.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-46442"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400",
      "CWE-835"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-05-24T20:09:40Z",
    "nvd_published_at": "2024-05-24T17:15:45Z",
    "severity": "HIGH"
  },
  "details": "An infinite loop in the retrieveActiveBody function of Soot before v4.4.1 under Java 8 allows attackers to cause a Denial of Service (DoS).",
  "id": "GHSA-hfg7-j82c-fr3w",
  "modified": "2024-08-22T21:40:37Z",
  "published": "2024-05-24T20:09:40Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-46442"
    },
    {
      "type": "WEB",
      "url": "https://github.com/JAckLosingHeart/CVE-2023-46442_POC/tree/main"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/soot-oss/soot"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Soot Infinite Loop vulnerability"
}
Mitigation
Architecture and Design

Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.

Mitigation
Architecture and Design
  • Mitigation of resource exhaustion attacks requires that the target system either:
  • The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
  • The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
  • recognizes the attack and denies that user further access for a given amount of time, or
  • uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Mitigation
Architecture and Design

Ensure that protocols have specific limits of scale placed on them.

Mitigation
Implementation

Ensure that all failures in resource allocation place the system into a safe posture.

CAPEC-147: XML Ping of the Death

An attacker initiates a resource depletion attack where a large number of small XML messages are delivered at a sufficiently rapid rate to cause a denial of service or crash of the target. Transactions such as repetitive SOAP transactions can deplete resources faster than a simple flooding attack because of the additional resources used by the SOAP protocol and the resources necessary to process SOAP messages. The transactions used are immaterial as long as they cause resource utilization on the target. In other words, this is a normal flooding attack augmented by using messages that will require extra processing on the target.

CAPEC-227: Sustained Client Engagement

An adversary attempts to deny legitimate users access to a resource by continually engaging a specific resource in an attempt to keep the resource tied up as long as possible. The adversary's primary goal is not to crash or flood the target, which would alert defenders; rather it is to repeatedly perform actions or abuse algorithmic flaws such that a given resource is tied up and not available to a legitimate user. By carefully crafting a requests that keep the resource engaged through what is seemingly benign requests, legitimate users are limited or completely denied access to the resource.

CAPEC-492: Regular Expression Exponential Blowup

An adversary may execute an attack on a program that uses a poor Regular Expression(Regex) implementation by choosing input that results in an extreme situation for the Regex. A typical extreme situation operates at exponential time compared to the input size. This is due to most implementations using a Nondeterministic Finite Automaton(NFA) state machine to be built by the Regex algorithm since NFA allows backtracking and thus more complex regular expressions.

← Back to the CWE list