GHSA-WHJ9-M24X-QHHP

Vulnerability from github – Published: 2023-06-22 20:00 – Updated: 2023-06-22 20:00
VLAI?
Summary
FastAsyncWorldEdit vulnerable to Uncontrolled Resource Consumption
Details

Coordinated Disclosure Timeline

  • 10.06.2023: Issue reported to IntellectualSites
  • 11.06.2023: Issue is acknowledged
  • 12.06.2023: Issue has been fixed
  • 22.06.2023: Advisory has been published

Impacted version range

Before 2.6.3

Details

Proof of Concept

As a user, do the following:

  1. Select position 1 via //pos1
  2. Select position 2 adding the "Infinity" keyword via //pos2 Infinity
  3. Execute any further operation.

The steps 1 and 2 are interchangeable.

Impact

Such a task has a possibility of bringing the performing server down.

CVE

  • CVE-2023-35925

Credit

This issue was discovered and reported by @SuperMonis.

Solution

On June 12, 2023, a patch, https://github.com/IntellectualSites/FastAsyncWorldEdit/pull/2285, has been merged addressing the vulnerability. We strongly recommend users to update their version of FastAsyncWorldEdit to 2.6.3 as soon as possible.

Workarounds

There is no direct mitigation besides updating FastAsyncWorldEdit to a patched version.

Additional Information

Users with access to the logs/ folder or shell access on their server can try to identify possible abuses of this issue by going through the logs. To sieve through the data, you can use the regex query \/\/pos[12] Infinity, then investigate all log entries that return results.

Disclosure Policy

If you discover a security vulnerability within our software, please report the issue according to our vulnerability disclosure policy.

Severity ?
6.2 (Medium)
CVSS:3.1/AV:L/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": "com.fastasyncworldedit:FastAsyncWorldEdit-Core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.6.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "com.fastasyncworldedit:FastAsyncWorldEdit-Bukkit"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.6.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-35925"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-06-22T20:00:36Z",
    "nvd_published_at": "2023-06-23T16:15:09Z",
    "severity": "MODERATE"
  },
  "details": "### Coordinated Disclosure Timeline\n\n- 10.06.2023: Issue reported to IntellectualSites\n- 11.06.2023: Issue is acknowledged\n- 12.06.2023: Issue has been fixed\n- 22.06.2023: Advisory has been published\n\n### Impacted version range\n\nBefore 2.6.3\n\n### Details\n\n#### Proof of Concept\n\nAs a user, do the following:\n\n1. Select position 1 via `//pos1`\n2. Select position 2 adding the \"Infinity\" keyword via `//pos2 Infinity`\n3. Execute any further operation.\n\nThe steps 1 and 2 are interchangeable.\n\n#### Impact\n\nSuch a task has a possibility of bringing the performing server down.\n\n#### CVE\n\n- CVE-2023-35925\n\n#### Credit\n\nThis issue was discovered and [reported](https://github.com/IntellectualSites/.github/blob/main/SECURITY.md) by @SuperMonis.\n\n### Solution\n\nOn June 12, 2023, a patch, https://github.com/IntellectualSites/FastAsyncWorldEdit/pull/2285, has been merged addressing the vulnerability.\nWe strongly recommend users to update their version of FastAsyncWorldEdit to 2.6.3 as soon as possible.\n\n### Workarounds\n\nThere is no direct mitigation besides updating FastAsyncWorldEdit to a patched version.\n\n### Additional Information\n\nUsers with access to the `logs/` folder or shell access on their server can try to identify possible abuses of this issue by going through the logs.\nTo sieve through the data, you can use the regex query `\\/\\/pos[12] Infinity`, then investigate all log entries that return results.\n\n### Disclosure Policy\n\nIf you discover a security vulnerability within our software, please report the issue according to our [vulnerability disclosure policy](https://github.com/IntellectualSites/.github/blob/main/SECURITY.md).",
  "id": "GHSA-whj9-m24x-qhhp",
  "modified": "2023-06-22T20:00:36Z",
  "published": "2023-06-22T20:00:36Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/IntellectualSites/FastAsyncWorldEdit/security/advisories/GHSA-whj9-m24x-qhhp"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-35925"
    },
    {
      "type": "WEB",
      "url": "https://github.com/IntellectualSites/FastAsyncWorldEdit/pull/2285"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/IntellectualSites/FastAsyncWorldEdit"
    },
    {
      "type": "WEB",
      "url": "https://github.com/IntellectualSites/FastAsyncWorldEdit/releases/tag/2.6.3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "FastAsyncWorldEdit vulnerable to Uncontrolled Resource Consumption"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.