{"answers":{"affected":"1 open source package ship an affected version, including drupal/core.","exploited":"There is no known exploitation of DRUPAL-CORE-2019-005 in the wild and no public exploit code.","fix":"Upgrade drupal/core to a fixed version for your release line: 8.5.15 or 8.6.15.","what":"DRUPAL-CORE-2019-005 is a code injection vulnerability in drupal/core, published on 17 Apr 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for DRUPAL-CORE-2019-005 and fix it if it is affected.\n\nWhat it is: DRUPAL-CORE-2019-005 is a code injection vulnerability in drupal/core, published on 17 Apr 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of DRUPAL-CORE-2019-005 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- drupal/core (Packagist): affected from 8.0.0; fixed in 8.5.15, 8.6.15\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/DRUPAL-CORE-2019-005/ (Markdown: https://insights.sbomify.com/DRUPAL-CORE-2019-005/index.md)","id":"DRUPAL-CORE-2019-005","markdown":"https://insights.sbomify.com/DRUPAL-CORE-2019-005/index.md","name":"DRUPAL-CORE-2019-005","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Drupal core","requires_auth":"low_privilege","summary":"Drupal core updates fix Symfony vulnerabilities allowing remote code execution and account takeover via unescaped input or cookie manipulation.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This security release fixes third-party dependencies included in or required by Drupal core.\n\n* [CVE-2019-10909: Escape validation messages in the PHP templating engine](https://symfony.com/blog/cve-2019-10909-escape-validation-messages-in-the-php-templating-engine). From that advisory:  \n  \u003e Validation messages were not escaped when using the form theme of the PHP templating engine which, when validation messages may contain user input, could result in an XSS.\n* [CVE-2019-10910: Check service IDs are valid](https://symfony.com/blog/cve-2019-10910-check-service-ids-are-valid). From that advisory:\n  \u003e Service IDs derived from unfiltered user input could result in the execution of any arbitrary code, resulting in possible remote code execution.\n* [CVE-2019-10911: Add a separator in the remember me cookie hash](https://symfony.com/blog/cve-2019-10911-add-a-separator-in-the-remember-me-cookie-hash). From that advisory:\n  \u003e This fixes situations where part of an expiry time in a cookie could be considered part of the username, or part of the username could be considered part of the expiry time. An attacker could modify the remember me cookie and authenticate as a different user. This attack is only possible if remember me functionality is enabled and the two users share a password hash or the password hashes (e.g. UserInterface::getPassword()) are null for all users (which is valid if passwords are checked by an external system, e.g. an SSO).","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"This security release fixes third-party dependencies included in or required by Drupal core.","id":"DRUPAL-CORE-2019-005","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["8.5.15","8.6.15"],"introduced":["8.0.0","8.6.0"],"last_affected":[],"package":"drupal/core","purl":"pkg:composer/drupal/core","source":"DRUPAL-CORE-2019-005"}],"products":null,"published":"2019-04-17","related":[],"sources":[{"class":"attribution","licence":"MIT","name":"Drupal","prefix":"DRUPAL"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Drupal core updates fix Symfony vulnerabilities allowing remote code execution and account takeover via unescaped input or cookie manipulation.","url":"https://insights.sbomify.com/DRUPAL-CORE-2019-005/"}