Vulnerability from drupal – Published: 2018-08-08 17:14 – Updated: 2023-08-11 21:24 – Source website
This module enables you to add or overwrite PHP configuration on a drupal website.
The module doesn't sufficiently allow access to set these configurations, leading to arbitrary PHP configuration execution by an attacker.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer phpconfig".
After updating the module, it's important to review the permissions of your website and if 'administer phpconfig' permission is given to a not fully trusted user role, we advise to revoke it.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.1.0"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/phpconfig"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.1.0"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.0"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [],
"credits": [
{
"contact": [
"https://www.drupal.org/u/tatarbj"
],
"name": "Balazs Janos Tatar"
}
],
"details": "This module enables you to add or overwrite PHP configuration on a drupal website.\n\nThe module doesn\u0027t sufficiently allow access to set these configurations, leading to arbitrary PHP configuration execution by an attacker.\n\nThis vulnerability is mitigated by the fact that an attacker must have a role with the permission \"administer phpconfig\".\n\nAfter updating the module, it\u0027s important to review the permissions of your website and if \u0027administer phpconfig\u0027 permission is given to a not fully trusted user role, we advise to revoke it.",
"id": "DRUPAL-CONTRIB-2018-055",
"modified": "2023-08-11T21:24:54.000Z",
"published": "2018-08-08T17:14:32.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2018-055"
}
],
"schema_version": "1.7.0"
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.