GHSA-4CPV-669C-R79X

Vulnerability from github – Published: 2023-09-11 14:43 – Updated: 2023-09-11 14:43
VLAI?
Summary
Prevent injection of invalid entity ids for "autocomplete" fields
Details

Impact

Under certain circumstances, an attacker could successfully submit an entity id for an EntityType that is not part of the valid choices.

Affected applications are any that use:

  • A custom query_builder option to limit the valid results; AND
  • An EntityType with 'autocomplete' => true or a custom AsEntityAutocompleteField.

Under this circumstance, if an id is submitted, it is accepted even if the matching record would not be returned by the custom query built with query_builder.

Patches

The problem has been fixed in symfony/ux-autocomplete version 2.11.2.

Workarounds

Upgrade to version 2.11.2 or greater of symfony/ux-autocomplete or perform extra validation after submit to verify the selected option is valid.

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

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "symfony/ux-autocomplete"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.11.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-41336"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-09-11T14:43:05Z",
    "nvd_published_at": "2023-09-11T20:15:10Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nUnder certain circumstances, an attacker could successfully submit an entity id for an `EntityType` that is *not* part of the valid choices.\n\nAffected applications are any that use:\n\n* A custom `query_builder` option to limit the valid results;\nAND\n* An `EntityType` with `\u0027autocomplete\u0027 =\u003e true` or a custom [AsEntityAutocompleteField](https://symfony.com/bundles/ux-autocomplete/current/index.html#usage-in-a-form-with-ajax).\n\nUnder this circumstance, if an id is submitted, it is accepted even if the matching record would not be returned by the custom query built with `query_builder`.\n\n### Patches\n\nThe problem has been fixed in `symfony/ux-autocomplete` version 2.11.2.\n\n### Workarounds\nUpgrade to version 2.11.2 or greater of `symfony/ux-autocomplete` or perform extra validation after submit to verify the selected option is valid.\n",
  "id": "GHSA-4cpv-669c-r79x",
  "modified": "2023-09-11T14:43:05Z",
  "published": "2023-09-11T14:43:05Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/symfony/ux-autocomplete/security/advisories/GHSA-4cpv-669c-r79x"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-41336"
    },
    {
      "type": "WEB",
      "url": "https://github.com/symfony/ux-autocomplete/commit/fabcb2eee14b9e84a45b276711853a560b5d770c"
    },
    {
      "type": "WEB",
      "url": "https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-autocomplete/CVE-2023-41336.yaml"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/symfony/ux-autocomplete"
    },
    {
      "type": "WEB",
      "url": "https://symfony.com/bundles/ux-autocomplete/current/index.html#usage-in-a-form-with-ajax"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Prevent injection of invalid entity ids for \"autocomplete\" fields"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.



Detection rules are retrieved from Rulezet.