CWE-22
Allowed-with-ReviewImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Abstraction: Base · Status: Stable
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
13131 vulnerabilities reference this CWE, most recent first.
GHSA-8PHM-9C2M-9HPQ
Vulnerability from github – Published: 2026-01-30 09:30 – Updated: 2026-01-30 09:30An input neutralization vulnerability in the File Operations API Endpoint component of Crafty Controller allows a remote, authenticated attacker to perform file tampering and remote code execution via path traversal.
{
"affected": [],
"aliases": [
"CVE-2026-0963"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-30T07:16:15Z",
"severity": "CRITICAL"
},
"details": "An input neutralization vulnerability in the File Operations API Endpoint component of Crafty Controller allows a remote, authenticated attacker to perform file tampering and remote code execution via path traversal.",
"id": "GHSA-8phm-9c2m-9hpq",
"modified": "2026-01-30T09:30:54Z",
"published": "2026-01-30T09:30:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0963"
},
{
"type": "WEB",
"url": "https://gitlab.com/crafty-controller/crafty-4/-/issues/660"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-8PJF-P5GM-5GQ6
Vulnerability from github – Published: 2026-04-23 00:31 – Updated: 2026-04-23 00:31A path Traversal vulnerability exists in Ziostation2 v2.9.8.7 and earlier. A remote unauthenticated attacker may get sensitive information on the operating system.
{
"affected": [],
"aliases": [
"CVE-2026-40062"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-23T00:16:45Z",
"severity": "HIGH"
},
"details": "A path Traversal vulnerability exists in Ziostation2 v2.9.8.7 and earlier. A remote unauthenticated attacker may get sensitive information on the operating system.",
"id": "GHSA-8pjf-p5gm-5gq6",
"modified": "2026-04-23T00:31:19Z",
"published": "2026-04-23T00:31:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40062"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/jp/JVN00575116"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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-8PJM-JGVR-53W9
Vulnerability from github – Published: 2026-03-31 09:31 – Updated: 2026-03-31 09:31A Path Traversal vulnerability affecting Factory Resource Management in DELMIA Factory Resource Manager from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2025x allows an attacker to read or write files in specific directories on the server.
{
"affected": [],
"aliases": [
"CVE-2025-10559"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-31T09:16:21Z",
"severity": "HIGH"
},
"details": "A Path Traversal vulnerability affecting Factory Resource Management in DELMIA Factory Resource Manager from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2025x allows an attacker to read or write files in specific directories on the server.",
"id": "GHSA-8pjm-jgvr-53w9",
"modified": "2026-03-31T09:31:41Z",
"published": "2026-03-31T09:31:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-10559"
},
{
"type": "WEB",
"url": "https://www.3ds.com/trust-center/security/security-advisories/cve-2025-10559"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-8PJP-4JF2-XRMW
Vulnerability from github – Published: 2022-05-01 23:29 – Updated: 2022-05-01 23:29Directory traversal vulnerability in info.php in GradMan 0.1.3 and earlier allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the tabla parameter, a different vector than CVE-2008-0361.
{
"affected": [],
"aliases": [
"CVE-2008-0393"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-01-23T03:00:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in info.php in GradMan 0.1.3 and earlier allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the tabla parameter, a different vector than CVE-2008-0361.",
"id": "GHSA-8pjp-4jf2-xrmw",
"modified": "2022-05-01T23:29:49Z",
"published": "2022-05-01T23:29:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-0393"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/39768"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/4936"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/28520"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/27343"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8PJX-JJ86-J47P
Vulnerability from github – Published: 2024-02-01 00:16 – Updated: 2025-10-22 19:08Today we are releasing Grafana 8.3.1, 8.2.7, 8.1.8, 8.0.7. This patch release includes a high severity security fix that affects Grafana versions from v8.0.0-beta1 through v8.3.0.
Release v8.3.1, only containing a security fix:
Release v8.2.7, only containing a security fix:
Release v8.1.8, only containing a security fix:
Release v8.0.7, only containing a security fix:
Path Traversal (CVE-2021-43798)
Summary
On 2021-12-03, we received a report that Grafana is vulnerable to directory traversal, allowing access to local files. We have confirmed this for versions 8.0.0-beta1 to 8.3.0. Thanks to our defense-in-depth approach, at no time has Grafana Cloud been vulnerable.
The vulnerable URL path is: /public/plugins//, where is the plugin ID for any installed plugin.
Every Grafana instance comes with pre-installed plugins like the Prometheus plugin or MySQL plugin so the following URLs are vulnerable for every instance:
- /public/plugins/alertlist/
- /public/plugins/annolist/
- /public/plugins/barchart/
- /public/plugins/bargauge/
- /public/plugins/candlestick/
- /public/plugins/cloudwatch/
- /public/plugins/dashlist/
- /public/plugins/elasticsearch/
- /public/plugins/gauge/
- /public/plugins/geomap/
- /public/plugins/gettingstarted/
- /public/plugins/grafana-azure-monitor-datasource/
- /public/plugins/graph/
- /public/plugins/heatmap/
- /public/plugins/histogram/
- /public/plugins/influxdb/
- /public/plugins/jaeger/
- /public/plugins/logs/
- /public/plugins/loki/
- /public/plugins/mssql/
- /public/plugins/mysql/
- /public/plugins/news/
- /public/plugins/nodeGraph/
- /public/plugins/opentsdb
- /public/plugins/piechart/
- /public/plugins/pluginlist/
- /public/plugins/postgres/
- /public/plugins/prometheus/
- /public/plugins/stackdriver/
- /public/plugins/stat/
- /public/plugins/state-timeline/
- /public/plugins/status-history/
- /public/plugins/table/
- /public/plugins/table-old/
- /public/plugins/tempo/
- /public/plugins/testdata/
- /public/plugins/text/
- /public/plugins/timeseries/
- /public/plugins/welcome/
- /public/plugins/zipkin/
We have received CVE-2021-43798 for this issue. The CVSS score for this vulnerability is 7.5 High (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) for Grafana versions 8.0.0-beta1 to 8.3.0
Affected versions with high severity
Grafana 8.0.0-beta1 to 8.3.0
Solutions and mitigations
All installations between v8.0.0-beta1 and v8.3.0 should be upgraded as soon as possible.
If you can not upgrade, running a reverse proxy in front of Grafana that normalizes the PATH of the request will mitigate the vulnerability. For example the normalize_path setting in envoy.
Thanks to our defense-in-depth approach, Grafana Cloud instances have not been affected by the vulnerability.
As always, we closely coordinated with all cloud providers licensed to offer Grafana Pro. They have received early notification under embargo and confirmed that their offerings are secure at the time of this announcement. In alphabetical order, this is applicable to Amazon Managed Grafana, and Azure Managed Grafana.
Timeline and postmortem
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
- 2021-12-03: Security researcher sends the initial report
- 2021-12-03: Confirmed for 8.0.0-beta1 through 8.3.0
- 2021-12-03: Confirmed that Grafana Cloud is not vulnerable
- 2021-12-03: Security fix determined and committed to Git
- 2021-12-03: Release timeline determined: 2021-12-07 for private customer release, 2021-12-14 for public release
- 2021-12-06: Second report about the vulnerability received
- 2021-12-07: We received information that the vulnerability has been leaked to the public, turning it into a 0 day
- 2021-12-07: Decision made to release as quickly as feasible
- 2021-12-07: Private release with reduced two hour grace period instead of the usual 1 week
- 2021-12-07: Public release
Acknowledgements
We would like to thank Jordy Versmissen for finding the vulnerability and alerting us to it.
Reporting security Issues
If you think you have found a security vulnerability, please send a report to security@grafana.com. This address can be used for all of Grafana Labs' open source and commercial products (including but not limited to Grafana, Grafana Cloud, Grafana Enterprise, and grafana.com). We can accept only vulnerability reports at this address. We would prefer that you encrypt your message to us by using our PGP key. The key fingerprint is
F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA
The key is available from keyserver.ubuntu.com.
Security announcements
We maintain a security category on our blog, where we will always post a summary, remediation, and mitigation details for any patch containing security fixes.
You can also subscribe to our RSS feed.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "8.3.0"
},
{
"fixed": "8.3.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "8.2.0"
},
{
"fixed": "8.2.7"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "8.1.0"
},
{
"fixed": "8.1.8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "8.0.0-beta1"
},
{
"fixed": "8.0.7"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-43798"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2024-02-01T00:16:10Z",
"nvd_published_at": "2021-12-07T19:15:00Z",
"severity": "HIGH"
},
"details": "Today we are releasing Grafana 8.3.1, 8.2.7, 8.1.8, 8.0.7. This patch release includes a high severity security fix that affects Grafana versions from v8.0.0-beta1 through v8.3.0.\n\nRelease v8.3.1, only containing a security fix:\n\n- [Download Grafana 8.3.1](https://grafana.com/grafana/download/8.3.1)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-3-1/)\n\nRelease v8.2.7, only containing a security fix:\n\n- [Download Grafana 8.2.7](https://grafana.com/grafana/download/8.2.7)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-2-7/)\n\nRelease v8.1.8, only containing a security fix:\n\n- [Download Grafana 8.1.8](https://grafana.com/grafana/download/8.1.8)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-8/)\n\nRelease v8.0.7, only containing a security fix:\n\n- [Download Grafana 8.0.7](https://grafana.com/grafana/download/8.0.7)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-0-7/)\n\n\n## Path Traversal ([CVE-2021-43798](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43798))\n\n### Summary \n\nOn 2021-12-03, we received a report that Grafana is vulnerable to directory traversal, allowing access to local files. We have confirmed this for versions 8.0.0-beta1 to 8.3.0. Thanks to our defense-in-depth approach, at no time has [Grafana Cloud](https://grafana.com/cloud) been vulnerable.\n\nThe vulnerable URL path is: \u003cgrafana_host_url\u003e/public/plugins/\u003cplugin-id\u003e/, where \u003cplugin-id\u003e is the plugin ID for any installed plugin.\n\nEvery Grafana instance comes with pre-installed plugins like the Prometheus plugin or MySQL plugin so the following URLs are vulnerable for every instance:\n\n* \u003cgrafana_host_url\u003e/public/plugins/alertlist/\n* \u003cgrafana_host_url\u003e/public/plugins/annolist/\n* \u003cgrafana_host_url\u003e/public/plugins/barchart/\n* \u003cgrafana_host_url\u003e/public/plugins/bargauge/\n* \u003cgrafana_host_url\u003e/public/plugins/candlestick/\n* \u003cgrafana_host_url\u003e/public/plugins/cloudwatch/\n* \u003cgrafana_host_url\u003e/public/plugins/dashlist/\n* \u003cgrafana_host_url\u003e/public/plugins/elasticsearch/\n* \u003cgrafana_host_url\u003e/public/plugins/gauge/\n* \u003cgrafana_host_url\u003e/public/plugins/geomap/\n* \u003cgrafana_host_url\u003e/public/plugins/gettingstarted/\n* \u003cgrafana_host_url\u003e/public/plugins/grafana-azure-monitor-datasource/\n* \u003cgrafana_host_url\u003e/public/plugins/graph/\n* \u003cgrafana_host_url\u003e/public/plugins/heatmap/\n* \u003cgrafana_host_url\u003e/public/plugins/histogram/\n* \u003cgrafana_host_url\u003e/public/plugins/influxdb/\n* \u003cgrafana_host_url\u003e/public/plugins/jaeger/\n* \u003cgrafana_host_url\u003e/public/plugins/logs/\n* \u003cgrafana_host_url\u003e/public/plugins/loki/\n* \u003cgrafana_host_url\u003e/public/plugins/mssql/\n* \u003cgrafana_host_url\u003e/public/plugins/mysql/\n* \u003cgrafana_host_url\u003e/public/plugins/news/\n* \u003cgrafana_host_url\u003e/public/plugins/nodeGraph/\n* \u003cgrafana_host_url\u003e/public/plugins/opentsdb\n* \u003cgrafana_host_url\u003e/public/plugins/piechart/\n* \u003cgrafana_host_url\u003e/public/plugins/pluginlist/\n* \u003cgrafana_host_url\u003e/public/plugins/postgres/\n* \u003cgrafana_host_url\u003e/public/plugins/prometheus/\n* \u003cgrafana_host_url\u003e/public/plugins/stackdriver/\n* \u003cgrafana_host_url\u003e/public/plugins/stat/\n* \u003cgrafana_host_url\u003e/public/plugins/state-timeline/\n* \u003cgrafana_host_url\u003e/public/plugins/status-history/\n* \u003cgrafana_host_url\u003e/public/plugins/table/\n* \u003cgrafana_host_url\u003e/public/plugins/table-old/\n* \u003cgrafana_host_url\u003e/public/plugins/tempo/\n* \u003cgrafana_host_url\u003e/public/plugins/testdata/\n* \u003cgrafana_host_url\u003e/public/plugins/text/\n* \u003cgrafana_host_url\u003e/public/plugins/timeseries/\n* \u003cgrafana_host_url\u003e/public/plugins/welcome/\n* \u003cgrafana_host_url\u003e/public/plugins/zipkin/\n\nWe have received CVE-2021-43798 for this issue. The CVSS score for this vulnerability is 7.5 High (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) for Grafana versions 8.0.0-beta1 to 8.3.0 \n\n### Affected versions with high severity \n\nGrafana 8.0.0-beta1 to 8.3.0\n\n### Solutions and mitigations\n\nAll installations between v8.0.0-beta1 and v8.3.0 should be upgraded as soon as possible.\n\nIf you can not upgrade, running a reverse proxy in front of Grafana that normalizes the PATH of the request will mitigate the vulnerability. For example the normalize_path setting in envoy.\n\nThanks to our defense-in-depth approach, [Grafana Cloud](https://grafana.com/cloud) instances have not been affected by the vulnerability.\n\nAs always, we closely coordinated with all cloud providers licensed to offer Grafana Pro. They have received early notification under embargo and confirmed that their offerings are secure at the time of this announcement. In alphabetical order, this is applicable to Amazon Managed Grafana, and Azure Managed Grafana.\n\n### Timeline and postmortem\n\nHere is a detailed timeline starting from when we originally learned of the issue. All times in UTC.\n\n* 2021-12-03: Security researcher sends the initial report\n* 2021-12-03: Confirmed for 8.0.0-beta1 through 8.3.0\n* 2021-12-03: Confirmed that Grafana Cloud is not vulnerable\n* 2021-12-03: Security fix determined and committed to Git\n* 2021-12-03: Release timeline determined: 2021-12-07 for private customer release, 2021-12-14 for public release\n* 2021-12-06: Second report about the vulnerability received\n* 2021-12-07: We received information that the vulnerability has been leaked to the public, turning it into a 0 day\n* 2021-12-07: Decision made to release as quickly as feasible\n* 2021-12-07: Private release with reduced two hour grace period instead of the usual 1 week\n* 2021-12-07: Public release\n\n### Acknowledgements\n\nWe would like to thank [Jordy Versmissen](https://twitter.com/j0v0x0) for finding the vulnerability and alerting us to it.\n\n## Reporting security Issues\n\nIf you think you have found a security vulnerability, please send a report to [security@grafana.com](mailto:security@grafana.com). This address can be used for all of\nGrafana Labs\u0027 open source and commercial products (including but not limited to Grafana, Grafana Cloud, Grafana Enterprise, and grafana.com). We can accept only vulnerability reports at this address. We would prefer that you encrypt your message to us by using our PGP key. The key fingerprint is\n\nF988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA\n\nThe key is available from [keyserver.ubuntu.com](https://keyserver.ubuntu.com/pks/lookup?search=0xF9887BEA027A049FAE8E5CAAD1258932BE24C5CA\u0026fingerprint=on\u0026op=index).\n\n## Security announcements\n\nWe maintain a [security category on our blog](https://grafana.com/tags/security/), where we will always post a summary, remediation, and mitigation details for any patch containing security fixes. \n\nYou can also subscribe to our [RSS feed](https://grafana.com/tags/security/index.xml).",
"id": "GHSA-8pjx-jj86-j47p",
"modified": "2025-10-22T19:08:39Z",
"published": "2024-02-01T00:16:10Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/grafana/grafana/security/advisories/GHSA-8pjx-jj86-j47p"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-43798"
},
{
"type": "WEB",
"url": "https://github.com/grafana/grafana/commit/c798c0e958d15d9cc7f27c72113d572fa58545ce"
},
{
"type": "PACKAGE",
"url": "https://github.com/grafana/grafana"
},
{
"type": "WEB",
"url": "https://grafana.com/blog/2021/12/08/an-update-on-0day-cve-2021-43798-grafana-directory-traversal"
},
{
"type": "WEB",
"url": "https://security.netapp.com/advisory/ntap-20211229-0004"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-43798"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/165198/Grafana-Arbitrary-File-Reading.html"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/165221/Grafana-8.3.0-Directory-Traversal-Arbitrary-File-Read.html"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2021/12/09/2"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2021/12/10/4"
}
],
"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/E:H",
"type": "CVSS_V3"
}
],
"summary": "Grafana path traversal"
}
GHSA-8PMX-2FWR-JP92
Vulnerability from github – Published: 2022-05-17 04:11 – Updated: 2022-05-17 04:11Directory traversal vulnerability in the web interface in Titan FTP Server before 10.40 build 1829 allows remote attackers to list all usernames via a Go action with a .. (dot dot) in the search-bar value.
{
"affected": [],
"aliases": [
"CVE-2014-1842"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-04-29T10:37:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in the web interface in Titan FTP Server before 10.40 build 1829 allows remote attackers to list all usernames via a Go action with a .. (dot dot) in the search-bar value.",
"id": "GHSA-8pmx-2fwr-jp92",
"modified": "2022-05-17T04:11:01Z",
"published": "2022-05-17T04:11:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-1842"
},
{
"type": "WEB",
"url": "http://archives.neohapsis.com/archives/fulldisclosure/2014-02/0092.html"
},
{
"type": "WEB",
"url": "http://www.exploit-db.com/exploits/31579"
},
{
"type": "WEB",
"url": "http://www.osvdb.org/103196"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8PPJ-M7PV-XFGV
Vulnerability from github – Published: 2022-04-29 03:02 – Updated: 2022-04-29 03:02Directory traversal vulnerability in Pablo Software Solutions Quick 'n Easy FTP Server 1.77, and possibly earlier versions, allows remote authenticated users to determine the existence of arbitrary files via a .. (dot dot) in the DEL command, which triggers different error messages depending on whether the file exists or not.
{
"affected": [],
"aliases": [
"CVE-2004-2747"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2004-12-31T05:00:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in Pablo Software Solutions Quick \u0027n Easy FTP Server 1.77, and possibly earlier versions, allows remote authenticated users to determine the existence of arbitrary files via a .. (dot dot) in the DEL command, which triggers different error messages depending on whether the file exists or not.",
"id": "GHSA-8ppj-m7pv-xfgv",
"modified": "2022-04-29T03:02:02Z",
"published": "2022-04-29T03:02:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2004-2747"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/10661"
},
{
"type": "WEB",
"url": "http://www.osvdb.org/3574"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/350224/30/21640/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/9443"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1008756"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8PPM-MWHC-2H38
Vulnerability from github – Published: 2024-04-09 18:30 – Updated: 2024-04-09 18:30Microsoft Defender for IoT Remote Code Execution Vulnerability
{
"affected": [],
"aliases": [
"CVE-2024-29053"
],
"database_specific": {
"cwe_ids": [
"CWE-22",
"CWE-36"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-04-09T17:15:58Z",
"severity": "HIGH"
},
"details": "Microsoft Defender for IoT Remote Code Execution Vulnerability",
"id": "GHSA-8ppm-mwhc-2h38",
"modified": "2024-04-09T18:30:27Z",
"published": "2024-04-09T18:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-29053"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-29053"
}
],
"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"
}
]
}
GHSA-8PR9-XH7F-37JJ
Vulnerability from github – Published: 2022-05-02 03:24 – Updated: 2022-05-02 03:24Directory traversal vulnerability in Mongoose 2.4 allows remote attackers to read arbitrary files via a .. (dot dot) in the URI.
{
"affected": [],
"aliases": [
"CVE-2009-1354"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-04-21T16:24:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in Mongoose 2.4 allows remote attackers to read arbitrary files via a .. (dot dot) in the URI.",
"id": "GHSA-8pr9-xh7f-37jj",
"modified": "2022-05-02T03:24:22Z",
"published": "2022-05-02T03:24:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-1354"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/49878"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/8428"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/502648/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/34510"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8PRR-6F8H-3J5J
Vulnerability from github – Published: 2022-05-01 23:33 – Updated: 2022-05-01 23:33Directory traversal vulnerability in view_member.php in Public Warehouse LightBlog 9.6 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the username parameter.
{
"affected": [],
"aliases": [
"CVE-2008-0840"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-02-20T21:44:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in view_member.php in Public Warehouse LightBlog 9.6 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the username parameter.",
"id": "GHSA-8prr-6f8h-3j5j",
"modified": "2022-05-01T23:33:46Z",
"published": "2022-05-01T23:33:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-0840"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/5140"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/29017"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/488283/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/27837"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2008/0621"
}
],
"schema_version": "1.4.0",
"severity": []
}
Mitigation MIT-5.1
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.
- Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation MIT-20.1
Strategy: Input Validation
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
- Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59). This includes:
- realpath() in C
- getCanonicalPath() in Java
- GetFullPath() in ASP.NET
- realpath() or abs_path() in Perl
- realpath() in PHP
Mitigation MIT-4
Strategy: Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
Mitigation MIT-29
Strategy: Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Mitigation MIT-17
Strategy: Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
Mitigation MIT-21.1
Strategy: Enforcement by Conversion
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
- For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-185] provide this capability.
Mitigation MIT-22
Strategy: Sandbox or Jail
- Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
- OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
- This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
- Be careful to avoid CWE-243 and other weaknesses related to jails.
Mitigation MIT-34
Strategy: Attack Surface Reduction
- Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.
- This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.
Mitigation MIT-39
- Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
- If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
- Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
- In the context of path traversal, error messages which disclose path information can help attackers craft the appropriate attack strings to move through the file system hierarchy.
Mitigation MIT-16
Strategy: Environment Hardening
When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
CAPEC-126: Path Traversal
An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.
CAPEC-64: Using Slashes and URL Encoding Combined to Bypass Validation Logic
This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
CAPEC-76: Manipulating Web Input to File System Calls
An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
CAPEC-78: Using Escaped Slashes in Alternate Encoding
This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
CAPEC-79: Using Slashes in Alternate Encoding
This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.