CWE-276
AllowedIncorrect Default Permissions
Abstraction: Base · Status: Draft
During installation, installed file permissions are set to allow anyone to modify those files.
2082 vulnerabilities reference this CWE, most recent first.
GHSA-X347-P9XC-Q762
Vulnerability from github – Published: 2026-05-26 13:30 – Updated: 2026-05-26 13:30The affected product creates a directory with insecure default permissions during administrative installation. This allows a low-privileged local attacker to modify a temporary file defining the components to be installed, enabling local privilege escalation by forcing the deployment of arbitrary components.
{
"affected": [],
"aliases": [
"CVE-2026-44468"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-26T08:16:21Z",
"severity": "HIGH"
},
"details": "The affected product creates a directory with insecure default permissions during administrative installation. This allows a low-privileged local attacker to modify a temporary file defining the components to be installed, enabling local privilege escalation by forcing the deployment of arbitrary components.",
"id": "GHSA-x347-p9xc-q762",
"modified": "2026-05-26T13:30:54Z",
"published": "2026-05-26T13:30:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44468"
},
{
"type": "WEB",
"url": "https://www.certvde.com/en/advisories/VDE-2026-055"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-X3FM-96G7-H798
Vulnerability from github – Published: 2021-12-03 00:00 – Updated: 2021-12-04 00:01Barracuda Network Access Client before 5.2.2 creates a Temporary File in a Directory with Insecure Permissions. This file is executed with SYSTEM privileges when an unprivileged user performs a repair operation.
{
"affected": [],
"aliases": [
"CVE-2021-42711"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-01T23:15:00Z",
"severity": "HIGH"
},
"details": "Barracuda Network Access Client before 5.2.2 creates a Temporary File in a Directory with Insecure Permissions. This file is executed with SYSTEM privileges when an unprivileged user performs a repair operation.",
"id": "GHSA-x3fm-96g7-h798",
"modified": "2021-12-04T00:01:18Z",
"published": "2021-12-03T00:00:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-42711"
},
{
"type": "WEB",
"url": "https://github.com/mandiant/Vulnerability-Disclosures/blob/master/MNDT-2021-0010/MNDT-2021-0010.md"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-X3MR-MM28-QG7M
Vulnerability from github – Published: 2025-05-30 21:30 – Updated: 2025-05-30 21:30An improper default permissions vulnerability was reported in Lenovo PC Manager that could allow a local attacker to elevate privileges.
{
"affected": [],
"aliases": [
"CVE-2025-2502"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-05-30T20:15:42Z",
"severity": "HIGH"
},
"details": "An improper default permissions vulnerability was reported in Lenovo PC Manager that could allow a local attacker to elevate privileges.",
"id": "GHSA-x3mr-mm28-qg7m",
"modified": "2025-05-30T21:30:57Z",
"published": "2025-05-30T21:30:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-2502"
},
{
"type": "WEB",
"url": "https://iknow.lenovo.com.cn/detail/428586"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-X3RC-H9V8-W5JQ
Vulnerability from github – Published: 2024-02-18 09:30 – Updated: 2024-08-01 15:31Permission control vulnerability in the calendarProvider module.Successful exploitation of this vulnerability may affect service confidentiality.
{
"affected": [],
"aliases": [
"CVE-2023-52379"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-18T07:15:09Z",
"severity": "HIGH"
},
"details": "Permission control vulnerability in the calendarProvider module.Successful exploitation of this vulnerability may affect service confidentiality.",
"id": "GHSA-x3rc-h9v8-w5jq",
"modified": "2024-08-01T15:31:26Z",
"published": "2024-02-18T09:30:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52379"
},
{
"type": "WEB",
"url": "https://consumer.huawei.com/en/support/bulletin/2024/2"
},
{
"type": "WEB",
"url": "https://device.harmonyos.com/cn/docs/security/update/security-bulletins-202402-0000001834855405"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-X3X3-7Q8C-M397
Vulnerability from github – Published: 2022-06-14 00:00 – Updated: 2022-06-28 00:00Power Distribution Units running on Powertek firmware (multiple brands) before 3.30.30 have an insecure permissions setting on the user.token field that is accessible to everyone through the /cgi/get_param.cgi HTTP API. This leads to disclosing active session ids of currently logged-in administrators. The session id can then be reused to act as the administrator, allowing reading of the cleartext password, or reconfiguring the device.
{
"affected": [],
"aliases": [
"CVE-2022-33175"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-06-13T18:15:00Z",
"severity": "CRITICAL"
},
"details": "Power Distribution Units running on Powertek firmware (multiple brands) before 3.30.30 have an insecure permissions setting on the user.token field that is accessible to everyone through the /cgi/get_param.cgi HTTP API. This leads to disclosing active session ids of currently logged-in administrators. The session id can then be reused to act as the administrator, allowing reading of the cleartext password, or reconfiguring the device.",
"id": "GHSA-x3x3-7q8c-m397",
"modified": "2022-06-28T00:00:55Z",
"published": "2022-06-14T00:00:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-33175"
},
{
"type": "WEB",
"url": "https://gynvael.coldwind.pl/?lang=en\u0026id=748"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-X4Q6-FXMG-XGCV
Vulnerability from github – Published: 2022-05-24 17:33 – Updated: 2022-05-24 17:33An attacker with physical access to a PAX Point Of Sale device with ProlinOS through 2.4.161.8859R can boot it in management mode, enable the XCB service, and then list, read, create, and overwrite files with MAINAPP permissions.
{
"affected": [],
"aliases": [
"CVE-2020-28044"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-11-02T21:15:00Z",
"severity": "HIGH"
},
"details": "An attacker with physical access to a PAX Point Of Sale device with ProlinOS through 2.4.161.8859R can boot it in management mode, enable the XCB service, and then list, read, create, and overwrite files with MAINAPP permissions.",
"id": "GHSA-x4q6-fxmg-xgcv",
"modified": "2022-05-24T17:33:01Z",
"published": "2022-05-24T17:33:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-28044"
},
{
"type": "WEB",
"url": "https://git.lsd.cat/g/pax-pwn"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-X5FR-7HHJ-34J3
Vulnerability from github – Published: 2023-12-15 03:46 – Updated: 2026-09-04 18:27Default table permissions in SurrealDB were FULL instead of NONE. This would lead to tables having FULL permissions for SELECT, CREATE, UPDATE and DELETE unless some other permissions were specified via the PERMISSIONS clause.
We have decided to treat this behaviour as a vulnerability due to its security implications, especially considering the lack of specific documentation and potential for confusion due to the INFO FOR DB statement previously not displaying default permissions. Treating it as a bug fix provides justification for a change in default behavior outside of a major release.
Impact
Any client authorized to query data in a SurrealDB instance will have full access to any tables that were defined with no explicit permissions and that are within its authorization scope (i.e. namespace or database), including creating, reading, updating and deleting data. This is specially relevant for SurrealDB instances allowing guest access with publicly exposed interfaces (e.g. HTTP REST API or WebSocket API), since a remote unauthenticated user may gain full access to any tables that were defined without any explicit permissions. Tables that were defined with explicit permissions using the PERMISSIONS clause are not affected.
Patches
- Version
1.0.1includes a patch for this specific issue. Later releases will also include the patch. - Version
1.1.0-beta.1and latest nightly releases already include the patch for this issue.
In patched versions:
- Tables defined after the patch without explicit permissions have
NONEpermissions. - Table permissions are always explicitly displayed with the
INFO FOR DBstatement.
Workarounds
In unpatched versions, this issue can be resolved by explicitly defining table permissions as shown in the following examples:
-- INSECURE EXAMPLE
-- DEFINE TABLE insecure;
-- SECURE EXAMPLE 1
DEFINE TABLE secure PERMISSIONS NONE;
-- SECURE EXAMPLE 2
DEFINE TABLE secure PERMISSIONS FOR SELECT, CREATE, UPDATE, DELETE NONE;
-- SECURE EXAMPLE 3
DEFINE TABLE secure PERMISSIONS FOR
SELECT WHERE user = $auth.id,
CREATE, UPDATE, DELETE NONE;
-- SECURE EXAMPLE 4
DEFINE TABLE secure PERMISSIONS
FOR select WHERE published = true OR user = $auth.id
FOR create, update WHERE user = $auth.id
FOR delete WHERE user = $auth.id OR $auth.admin = true;
References
- https://github.com/surrealdb/surrealdb/pull/3074
- https://github.com/surrealdb/surrealdb/pull/3083
- https://github.com/surrealdb/surrealdb/pull/3125
- https://docs.surrealdb.com/docs/surrealql/statements/define/table/
- https://docs.surrealdb.com/docs/security/capabilities#guest-access
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "surrealdb"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-54366"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": true,
"github_reviewed_at": "2023-12-15T03:46:36Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "Default table permissions in SurrealDB were `FULL` instead of `NONE`. This would lead to tables having `FULL` permissions for `SELECT`, `CREATE`, `UPDATE` and `DELETE` unless some other permissions were specified via the `PERMISSIONS` clause.\n\nWe have decided to treat this behaviour as a vulnerability due to its security implications, especially considering the lack of specific documentation and potential for confusion due to the `INFO FOR DB` statement previously not displaying default permissions. Treating it as a bug fix provides justification for a change in default behavior outside of a major release.\n\n### Impact\n\nAny client authorized to query data in a SurrealDB instance will have full access to any tables that were defined with no explicit permissions and that are within its authorization scope (i.e. namespace or database), including creating, reading, updating and deleting data. This is specially relevant for SurrealDB instances allowing guest access with publicly exposed interfaces (e.g. HTTP REST API or WebSocket API), since a remote unauthenticated user may gain full access to any tables that were defined without any explicit permissions. Tables that were defined with explicit permissions using the `PERMISSIONS` clause are not affected.\n\n### Patches\n\n- Version `1.0.1` includes a patch for this specific issue. Later releases will also include the patch.\n- Version `1.1.0-beta.1` and latest nightly releases already include the patch for this issue.\n\nIn patched versions:\n\n- Tables defined after the patch without explicit permissions have `NONE` permissions.\n- Table permissions are always explicitly displayed with the `INFO FOR DB` statement.\n\n### Workarounds\n\nIn unpatched versions, this issue can be resolved by explicitly defining table permissions as shown in the following examples:\n\n```sql\n-- INSECURE EXAMPLE\n-- DEFINE TABLE insecure;\n-- SECURE EXAMPLE 1\nDEFINE TABLE secure PERMISSIONS NONE;\n-- SECURE EXAMPLE 2\nDEFINE TABLE secure PERMISSIONS FOR SELECT, CREATE, UPDATE, DELETE NONE;\n-- SECURE EXAMPLE 3\nDEFINE TABLE secure PERMISSIONS FOR\n SELECT WHERE user = $auth.id,\n CREATE, UPDATE, DELETE NONE;\n-- SECURE EXAMPLE 4\nDEFINE TABLE secure PERMISSIONS\n FOR select WHERE published = true OR user = $auth.id\n FOR create, update WHERE user = $auth.id\n FOR delete WHERE user = $auth.id OR $auth.admin = true;\n```\n\n### References\n\n- https://github.com/surrealdb/surrealdb/pull/3074\n- https://github.com/surrealdb/surrealdb/pull/3083\n- https://github.com/surrealdb/surrealdb/pull/3125\n- https://docs.surrealdb.com/docs/surrealql/statements/define/table/\n- https://docs.surrealdb.com/docs/security/capabilities#guest-access",
"id": "GHSA-x5fr-7hhj-34j3",
"modified": "2026-09-04T18:27:59Z",
"published": "2023-12-15T03:46:36Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/surrealdb/surrealdb/security/advisories/GHSA-x5fr-7hhj-34j3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54366"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/surrealdb/PYSEC-2026-3718.yaml"
},
{
"type": "PACKAGE",
"url": "https://github.com/surrealdb/surrealdb"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/surrealdb-before-insecure-default-table-permissions"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "SurrealDB: Full Table Permissions by Default"
}
GHSA-X6JP-2C5W-VPFG
Vulnerability from github – Published: 2022-05-24 19:03 – Updated: 2022-06-04 00:00jitsi-meet-prosody in Jitsi Meet before 5026 does not ensure that restrict_room_creation is set by default.
{
"affected": [],
"aliases": [
"CVE-2021-33506"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-05-26T15:15:00Z",
"severity": "HIGH"
},
"details": "jitsi-meet-prosody in Jitsi Meet before 5026 does not ensure that restrict_room_creation is set by default.",
"id": "GHSA-x6jp-2c5w-vpfg",
"modified": "2022-06-04T00:00:30Z",
"published": "2022-05-24T19:03:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-33506"
},
{
"type": "WEB",
"url": "https://github.com/jitsi/jitsi-meet/pull/9252/files"
},
{
"type": "WEB",
"url": "https://github.com/jitsi/jitsi-meet/compare/5025...5026"
},
{
"type": "WEB",
"url": "https://github.com/jitsi/security-advisories/blob/master/advisories/JSA-2021-0001.md"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-X6PH-R535-3VJW
Vulnerability from github – Published: 2025-07-18 20:03 – Updated: 2025-07-18 20:03It was discovered that the ld.so.cache in images generated by apko had file system permissions mode 0666:
bash-5.3# find / -type f -perm -o+w
/etc/ld.so.cache
This issue was introduced in commit 04f37e2 ("generate /etc/ld.so.cache (#1629)")(v0.27.0).
Impact
This potentially allows a local unprivileged user to add additional additional directories including dynamic libraries to the dynamic loader path. A user could exploit this by placing a malicious library in a directory they control.
Patches
This issue was addressed in apko in aedb077 ("fix: /etc/ld.so.cache file permissions (#1758)") (v0.29.5).
Acknowledgements
Many thanks to Cody Harris from H2O.ai for reporting this issue.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "chainguard.dev/apko"
},
"ranges": [
{
"events": [
{
"introduced": "0.27.0"
},
{
"fixed": "0.29.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-53945"
],
"database_specific": {
"cwe_ids": [
"CWE-276"
],
"github_reviewed": true,
"github_reviewed_at": "2025-07-18T20:03:25Z",
"nvd_published_at": "2025-07-18T16:15:30Z",
"severity": "HIGH"
},
"details": "It was discovered that the ld.so.cache in images generated by apko had file system permissions mode `0666`:\n```\nbash-5.3# find / -type f -perm -o+w\n/etc/ld.so.cache\n```\n\nThis issue was introduced in commit [04f37e2 (\"generate /etc/ld.so.cache (#1629)\")](https://github.com/chainguard-dev/apko/commit/04f37e2d50d5a502e155788561fb7d40de705bd9)([v0.27.0](https://github.com/chainguard-dev/apko/releases/tag/v0.27.0)).\n\n### Impact\nThis potentially allows a local unprivileged user to add additional additional directories including dynamic libraries to the dynamic loader path. A user could exploit this by placing a malicious library in a directory they control.\n\n### Patches\nThis issue was addressed in apko in [aedb077 (\"fix: /etc/ld.so.cache file permissions (#1758)\")](https://github.com/chainguard-dev/apko/commit/aedb0772d6bf6e74d8f17690946dbc791d0f6af3) ([v0.29.5](https://github.com/chainguard-dev/apko/releases/tag/v0.29.5)).\n\n### Acknowledgements\n\nMany thanks to Cody Harris from [H2O.ai](http://h2o.ai/) for reporting this issue.",
"id": "GHSA-x6ph-r535-3vjw",
"modified": "2025-07-18T20:03:25Z",
"published": "2025-07-18T20:03:25Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-x6ph-r535-3vjw"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-53945"
},
{
"type": "WEB",
"url": "https://github.com/chainguard-dev/apko/commit/04f37e2d50d5a502e155788561fb7d40de705bd9"
},
{
"type": "WEB",
"url": "https://github.com/chainguard-dev/apko/commit/aedb0772d6bf6e74d8f17690946dbc791d0f6af3"
},
{
"type": "PACKAGE",
"url": "https://github.com/chainguard-dev/apko"
},
{
"type": "WEB",
"url": "https://github.com/chainguard-dev/apko/releases/tag/v0.29.5"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "apko is vulnerable to attack through incorrect permissions in /etc/ld.so.cache and other files"
}
GHSA-X6WJ-WW64-PH44
Vulnerability from github – Published: 2022-05-24 17:42 – Updated: 2022-05-24 17:42An exploitable local privilege elevation vulnerability exists in the file system permissions of Advantech WebAccess/SCADA 9.0.1 installation. In privilege escalation via multiple service executables in installation folder of WebAccess, an attacker can either replace binary or loaded modules to execute code with NT SYSTEM privilege.
{
"affected": [],
"aliases": [
"CVE-2020-13552"
],
"database_specific": {
"cwe_ids": [
"CWE-269",
"CWE-276"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-02-17T19:15:00Z",
"severity": "HIGH"
},
"details": "An exploitable local privilege elevation vulnerability exists in the file system permissions of Advantech WebAccess/SCADA 9.0.1 installation. In privilege escalation via multiple service executables in installation folder of WebAccess, an attacker can either replace binary or loaded modules to execute code with NT SYSTEM privilege.",
"id": "GHSA-x6wj-ww64-ph44",
"modified": "2022-05-24T17:42:26Z",
"published": "2022-05-24T17:42:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-13552"
},
{
"type": "WEB",
"url": "https://talosintelligence.com/vulnerability_reports/TALOS-2020-1169"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-1
The architecture needs to access and modification attributes for files to only those users who actually require those actions.
Mitigation MIT-46
Strategy: Separation of Privilege
- Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs
In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
CAPEC-127: Directory Indexing
An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
CAPEC-81: Web Server Logs Tampering
Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to "Log Injection-Tampering-Forging" except that in this case, the attack is targeting the logs of the web server and not the application.