GHSA-3MWQ-H3G6-FFHM

Vulnerability from github – Published: 2023-10-05 20:55 – Updated: 2024-02-09 00:31
VLAI?
Summary
Vapor's incorrect request error handling triggers server crash
Details

Vapor incorrectly handles errors encountered during parsing of HTTP 1.x requests, triggering a precondition failure in swift-nio due to API misuse and causing immediate termination of the server process.

Impact

This is a denial of service vulnerability, impacting all users of affected versions of Vapor. Because the crash is an explicit assertion failure, there is no corruption of process state and no risk of data leakage or unauthorized code execution. Total impact is limited to an immediately recoverable service interruption.

Patches

The issue is fixed as of Vapor release 4.84.2.

Workarounds

None known at this time.

For more information

If you have any questions or comments about this advisory: * Open an issue in the Vapor repo * Ask in Vapor Discord

Acknowledgements

Full credit for reporting this issue goes to @t0rchwo0d, with additional thanks for responsibly disclosing.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "SwiftURL",
        "name": "github.com/vapor/vapor"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "4.83.2"
            },
            {
              "fixed": "4.84.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-44386"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-231"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-10-05T20:55:58Z",
    "nvd_published_at": "2023-10-05T18:15:12Z",
    "severity": "MODERATE"
  },
  "details": "Vapor incorrectly handles errors encountered during parsing of HTTP 1.x requests, triggering a precondition failure in swift-nio due to API misuse and causing immediate termination of the server process.\n\n### Impact\nThis is a denial of service vulnerability, impacting all users of affected versions of Vapor. Because the crash is an explicit assertion failure, there is no corruption of process state and no risk of data leakage or unauthorized code execution. Total impact is limited to an immediately recoverable service interruption.\n\n### Patches\nThe issue is fixed as of Vapor release 4.84.2.\n\n### Workarounds\nNone known at this time.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Vapor repo](https://github.com/vapor/vapor)\n* Ask in [Vapor Discord](http://vapor.team)\n\n### Acknowledgements\n\nFull credit for reporting this issue goes to @t0rchwo0d, with additional thanks for responsibly disclosing.",
  "id": "GHSA-3mwq-h3g6-ffhm",
  "modified": "2024-02-09T00:31:39Z",
  "published": "2023-10-05T20:55:58Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/vapor/vapor/security/advisories/GHSA-3mwq-h3g6-ffhm"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-44386"
    },
    {
      "type": "WEB",
      "url": "https://github.com/vapor/vapor/commit/090464a654b03148b139a81f8f5ac63b0856f6f3"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/vapor/vapor"
    },
    {
      "type": "WEB",
      "url": "https://github.com/vapor/vapor/releases/tag/4.84.2"
    }
  ],
  "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:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Vapor\u0027s incorrect request error handling triggers server crash"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…