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.
13051 vulnerabilities reference this CWE, most recent first.
GHSA-4JVG-4JFX-FMHC
Vulnerability from github – Published: 2026-06-18 15:04 – Updated: 2026-06-18 15:04Summary
The Sentry exporter constructs Sentry API URLs by interpolating the span's service.name resource attribute into the URL path without validation. Because service.name is controlled by remote OTLP senders and the operator-configured bearer token is attached to every request, a crafted service name can reach arbitrary Sentry API endpoints reachable by that token — including privileged admin, organization, and member endpoints within the configured Sentry organization.
Affected
- exporter/sentryexporter/sentry_exporter.go (lines 715–737) — extractProjectSlug returns the attacker-controlled service.name directly as the slug.
- exporter/sentryexporter/sentry_exporter.go (lines 745–809) — getOrCreateProjectEndpoint passes the raw slug to GetOTLPEndpoints at line 761.
- exporter/sentryexporter/sentry_client.go (lines 190–244) — GetProjectKeys interpolates the slug into fmt.Sprintf URL path and attaches the operator bearer token on line 207.
- exporter/sentryexporter/sentry_client.go (lines 327–363) — GetOTLPEndpoints calls GetProjectKeys on line 329 with the raw slug.
- exporter/sentryexporter/config.go (lines 55–108) — projectSlugRegexp is applied only to operator config mappings inside validateRoutingConfig, never to
runtime-derived slugs.
Root cause
- extractProjectSlug (sentry_exporter.go:715–737) reads service.name from pcommon.Resource.Attributes() without schema validation and returns the raw
string on line 736. - GetProjectKeys (sentry_client.go:192) calls fmt.Sprintf("%s/api/0/projects/%s/%s/keys/", c.baseURL, orgSlug, projectSlug). The slug is treated as a single path segment but no validation is performed.
- projectSlugRegexp (config.go:58) — defined as ^[a-z0-9_-]{1,50}$ — is referenced only inside validateRoutingConfig on line 98 (config-time only). No runtime callsite exists.
- Go net/http preserves literal .. and / characters in URL paths when constructed via fmt.Sprintf.
- The operator-configured DSN / bearer token is attached unconditionally to every outbound request (sentry_client.go:207): req.Header.Set("Authorization", fmt.Sprintf("Bearer %s", c.authToken)).
Exploitation
Primary: query-string injection (reliable across all deployments)
Attacker emits service.name = "foo?injected_query=".
URL becomes https://sentry.io/api/0/projects/ORG-SLUG/foo?injected_query=/keys/.
The trailing /keys/ is consumed as part of the query string. The resource endpoint is /api/0/projects/ORG-SLUG/foo. The attacker can reach any GET-based
Sentry API endpoint reachable by the bearer token. This vector is not dependent on server-side path normalization and works in all deployment
configurations.
Secondary: path traversal (nginx-dependent)
Attacker emits a span with service.name = "foo/../../members".
Resulting URL: https://sentry.io/api/0/projects/ORG-SLUG/foo/../../members/keys/
After server-side normalization (nginx resolves .. segments): https://sentry.io/api/0/projects/ORG-SLUG/members/keys/
The operator bearer token authenticates the request. Effectiveness depends on whether the Sentry deployment normalizes .. segments before routing (standard nginx behaviour).
Amplified: telemetry redirect for data exfiltration
Attacker-owned Sentry project slug → span data for other applications is exported to an attacker-controlled Sentry project, leaking operational telemetry.
The collector fetches the DSN/keys for the attacker's slug and subsequently forwards legitimate traces/logs to the attacker-controlled destination.
Threat model
- Attacker capabilities: remote OTLP trace sender (application-level span emission).
- Operator capabilities: configures Sentry DSN, bearer token, base URL; sets up receiver pipeline.
- The attacker does NOT control operator YAML. The attacker DOES control resource attribute values on spans they emit.
Realistic deployment
- Kubernetes cluster with OpenTelemetry Collector forwarding traces from multiple applications to Sentry SaaS or self-hosted Sentry.
- One compromised or malicious application reaches the collector via OTLP.
- The collector is configured with a valid Sentry bearer token for the organization.
Remediation
Apply the existing projectSlugRegexp to runtime-derived slugs, not only to operator config mappings:
```
import "regexp"
var runtimeSlugPattern = regexp.MustCompile(^[a-zA-Z0-9_-]+$)
func (s *endpointState) extractProjectSlug(attrs pcommon.Map) string {
attrValue, exists := attrs.Get(s.attributeKey)
if !exists || attrValue.Type() != pcommon.ValueTypeStr {
return ""
}
serviceName := attrValue.Str()
if serviceName == "" {
return ""
}
if s.projectMapping != nil {
if mappedSlug, ok := s.projectMapping[serviceName]; ok {
return mappedSlug
}
}
if !runtimeSlugPattern.MatchString(serviceName) {
return "" // reject; drop the span or use a fallback default project
}
return serviceName
}
Alternatively, reject at URL construction:
func (c *sentryClient) GetProjectKeys(ctx context.Context, orgSlug, projectSlug string) ([]projectKey, error) {
if !runtimeSlugPattern.MatchString(projectSlug) {
return nil, fmt.Errorf("invalid project slug: %q", projectSlug)
}
baseURL := fmt.Sprintf("%s/api/0/projects/%s/%s/keys/", c.baseURL, orgSlug, projectSlug)
// ...
}
```
Apply the runtime regex to ALL slug-derived URL components (including orgSlug if it can ever be attacker-influenced), not just to config-time validation.
Credit
Reported by independent security research by Martin Brodeur.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.154.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-47256"
],
"database_specific": {
"cwe_ids": [
"CWE-22",
"CWE-74"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-18T15:04:10Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "Summary \n \n The Sentry exporter constructs Sentry API URLs by interpolating the span\u0027s service.name resource attribute into the URL path without validation. Because\n service.name is controlled by remote OTLP senders and the operator-configured bearer token is attached to every request, a crafted service name can reach\n arbitrary Sentry API endpoints reachable by that token \u2014 including privileged admin, organization, and member endpoints within the configured Sentry\n organization. \n \n Affected \n \n - exporter/sentryexporter/sentry_exporter.go (lines 715\u2013737) \u2014 extractProjectSlug returns the attacker-controlled service.name directly as the slug. \n - exporter/sentryexporter/sentry_exporter.go (lines 745\u2013809) \u2014 getOrCreateProjectEndpoint passes the raw slug to GetOTLPEndpoints at line 761. \n - exporter/sentryexporter/sentry_client.go (lines 190\u2013244) \u2014 GetProjectKeys interpolates the slug into fmt.Sprintf URL path and attaches the operator bearer\n token on line 207. \n - exporter/sentryexporter/sentry_client.go (lines 327\u2013363) \u2014 GetOTLPEndpoints calls GetProjectKeys on line 329 with the raw slug.\n - exporter/sentryexporter/config.go (lines 55\u2013108) \u2014 projectSlugRegexp is applied only to operator config mappings inside validateRoutingConfig, never to \n runtime-derived slugs. \n \n Root cause \n \n 1. extractProjectSlug (sentry_exporter.go:715\u2013737) reads service.name from pcommon.Resource.Attributes() without schema validation and returns the raw \n string on line 736. \n 2. GetProjectKeys (sentry_client.go:192) calls fmt.Sprintf(\"%s/api/0/projects/%s/%s/keys/\", c.baseURL, orgSlug, projectSlug). The slug is treated as a\n single path segment but no validation is performed. \n 3. projectSlugRegexp (config.go:58) \u2014 defined as ^[a-z0-9_-]{1,50}$ \u2014 is referenced only inside validateRoutingConfig on line 98 (config-time only). No\n runtime callsite exists. \n 4. Go net/http preserves literal .. and / characters in URL paths when constructed via fmt.Sprintf. \n 5. The operator-configured DSN / bearer token is attached unconditionally to every outbound request (sentry_client.go:207): req.Header.Set(\"Authorization\", \n fmt.Sprintf(\"Bearer %s\", c.authToken)). \n \n Exploitation \n \n Primary: query-string injection (reliable across all deployments) \n \n Attacker emits service.name = \"foo?injected_query=\".\n \n URL becomes https://sentry.io/api/0/projects/ORG-SLUG/foo?injected_query=/keys/.\n \n The trailing /keys/ is consumed as part of the query string. The resource endpoint is /api/0/projects/ORG-SLUG/foo. The attacker can reach any GET-based\n Sentry API endpoint reachable by the bearer token. This vector is not dependent on server-side path normalization and works in all deployment \n configurations. \n \n Secondary: path traversal (nginx-dependent)\n \n Attacker emits a span with service.name = \"foo/../../members\".\n \n Resulting URL: https://sentry.io/api/0/projects/ORG-SLUG/foo/../../members/keys/\n \n After server-side normalization (nginx resolves .. segments): https://sentry.io/api/0/projects/ORG-SLUG/members/keys/\n \n The operator bearer token authenticates the request. Effectiveness depends on whether the Sentry deployment normalizes .. segments before routing (standard\n nginx behaviour). \n \n Amplified: telemetry redirect for data exfiltration \n \n Attacker-owned Sentry project slug \u2192 span data for other applications is exported to an attacker-controlled Sentry project, leaking operational telemetry. \n The collector fetches the DSN/keys for the attacker\u0027s slug and subsequently forwards legitimate traces/logs to the attacker-controlled destination. \n \n Threat model \n \n - Attacker capabilities: remote OTLP trace sender (application-level span emission). \n - Operator capabilities: configures Sentry DSN, bearer token, base URL; sets up receiver pipeline.\n - The attacker does NOT control operator YAML. The attacker DOES control resource attribute values on spans they emit.\n \n Realistic deployment\n \n - Kubernetes cluster with OpenTelemetry Collector forwarding traces from multiple applications to Sentry SaaS or self-hosted Sentry.\n - One compromised or malicious application reaches the collector via OTLP. \n - The collector is configured with a valid Sentry bearer token for the organization.\n\n \n Remediation\n \n Apply the existing projectSlugRegexp to runtime-derived slugs, not only to operator config mappings:\n ``` \n import \"regexp\" \n\n var runtimeSlugPattern = regexp.MustCompile(`^[a-zA-Z0-9_-]+$`)\n \n func (s *endpointState) extractProjectSlug(attrs pcommon.Map) string {\n attrValue, exists := attrs.Get(s.attributeKey) \n if !exists || attrValue.Type() != pcommon.ValueTypeStr {\n return \"\" \n } \n serviceName := attrValue.Str() \n if serviceName == \"\" {\n return \"\" \n } \n if s.projectMapping != nil {\n if mappedSlug, ok := s.projectMapping[serviceName]; ok { \n return mappedSlug\n } \n } \n if !runtimeSlugPattern.MatchString(serviceName) {\n return \"\" // reject; drop the span or use a fallback default project\n }\n return serviceName \n }\n \n Alternatively, reject at URL construction: \n \n func (c *sentryClient) GetProjectKeys(ctx context.Context, orgSlug, projectSlug string) ([]projectKey, error) {\n if !runtimeSlugPattern.MatchString(projectSlug) { \n return nil, fmt.Errorf(\"invalid project slug: %q\", projectSlug)\n } \n baseURL := fmt.Sprintf(\"%s/api/0/projects/%s/%s/keys/\", c.baseURL, orgSlug, projectSlug)\n // ... \n } \n``` \n Apply the runtime regex to ALL slug-derived URL components (including orgSlug if it can ever be attacker-influenced), not just to config-time validation. \n \n Credit \n \n Reported by independent security research by Martin Brodeur.",
"id": "GHSA-4jvg-4jfx-fmhc",
"modified": "2026-06-18T15:04:10Z",
"published": "2026-06-18T15:04:10Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/open-telemetry/opentelemetry-collector-contrib/security/advisories/GHSA-4jvg-4jfx-fmhc"
},
{
"type": "PACKAGE",
"url": "https://github.com/open-telemetry/opentelemetry-collector-contrib"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "opentelemetry-collector-contrib sentryexporter: Path traversal in Sentry exporter via attacker-controlled service.name reaches privileged Sentry API endpoints with operator bearer token"
}
GHSA-4JVJ-CX62-Q838
Vulnerability from github – Published: 2025-07-23 06:33 – Updated: 2025-07-23 06:33Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Samsung Electronics MagicINFO 9 Server allows Upload a Web Shell to a Web Server.This issue affects MagicINFO 9 Server: less than 21.1080.0
{
"affected": [],
"aliases": [
"CVE-2025-54443"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-07-23T06:15:26Z",
"severity": "CRITICAL"
},
"details": "Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027) vulnerability in Samsung Electronics MagicINFO 9 Server allows Upload a Web Shell to a Web Server.This issue affects MagicINFO 9 Server: less than 21.1080.0",
"id": "GHSA-4jvj-cx62-q838",
"modified": "2025-07-23T06:33:51Z",
"published": "2025-07-23T06:33:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54443"
},
{
"type": "WEB",
"url": "https://security.samsungtv.com/securityUpdates"
}
],
"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-4JVM-JP36-77CR
Vulnerability from github – Published: 2024-11-18 12:30 – Updated: 2024-11-18 12:30A low privileged remote attacker can overwrite an arbitrary file on the filesystem leading to a DoS and data loss.
{
"affected": [],
"aliases": [
"CVE-2024-41971"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-18T10:15:05Z",
"severity": "HIGH"
},
"details": "A low privileged remote attacker can overwrite an arbitrary file on the filesystem leading to a DoS and data loss.",
"id": "GHSA-4jvm-jp36-77cr",
"modified": "2024-11-18T12:30:42Z",
"published": "2024-11-18T12:30:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41971"
},
{
"type": "WEB",
"url": "https://cert.vde.com/en/advisories/VDE-2024-047"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-4JWW-MHXC-7MMM
Vulnerability from github – Published: 2022-05-01 07:44 – Updated: 2022-05-01 07:44Multiple directory traversal vulnerabilities in Kubix 0.7 and earlier allow remote attackers to (1) include and execute arbitrary local files via ".." sequences in the theme cookie to index.php, which is not properly handled by includes/head.php; and (2) read arbitrary files via ".." sequences in the file parameter in an add_dl action to adm_index.php, as demonstrated by reading connect.php.
{
"affected": [],
"aliases": [
"CVE-2006-7117"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2007-03-06T01:19:00Z",
"severity": "MODERATE"
},
"details": "Multiple directory traversal vulnerabilities in Kubix 0.7 and earlier allow remote attackers to (1) include and execute arbitrary local files via \"..\" sequences in the theme cookie to index.php, which is not properly handled by includes/head.php; and (2) read arbitrary files via \"..\" sequences in the file parameter in an add_dl action to adm_index.php, as demonstrated by reading connect.php.",
"id": "GHSA-4jww-mhxc-7mmm",
"modified": "2022-05-01T07:44:51Z",
"published": "2022-05-01T07:44:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2006-7117"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/30570"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/30572"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/2863"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/21352"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-4M29-HPFX-HXJV
Vulnerability from github – Published: 2026-04-29 18:31 – Updated: 2026-04-29 18:31A vulnerability was identified in NousResearch hermes-agent 0.8.0. Affected by this issue is some unknown functionality of the file gateway/platforms/wecom.py of the component WeChat Work Platform Adapter. The manipulation leads to path traversal. It is possible to initiate the attack remotely. The exploit is publicly available and might be used.
{
"affected": [],
"aliases": [
"CVE-2026-7396"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-29T18:16:05Z",
"severity": "MODERATE"
},
"details": "A vulnerability was identified in NousResearch hermes-agent 0.8.0. Affected by this issue is some unknown functionality of the file gateway/platforms/wecom.py of the component WeChat Work Platform Adapter. The manipulation leads to path traversal. It is possible to initiate the attack remotely. The exploit is publicly available and might be used.",
"id": "GHSA-4m29-hpfx-hxjv",
"modified": "2026-04-29T18:31:36Z",
"published": "2026-04-29T18:31:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-7396"
},
{
"type": "WEB",
"url": "https://github.com/NousResearch/hermes-agent/issues/8733"
},
{
"type": "WEB",
"url": "https://github.com/bugmaker2/hermes-agent/issues/29"
},
{
"type": "WEB",
"url": "https://github.com/NousResearch/hermes-agent"
},
{
"type": "WEB",
"url": "https://vuldb.com/submit/803269"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/360120"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/360120/cti"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/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-4M2V-GMF9-56QJ
Vulnerability from github – Published: 2025-06-26 18:31 – Updated: 2025-06-26 18:31A path traversal vulnerability exists in the web management interface of D-Link DSL-2730U, DSL-2750U, and DSL-2750E ADSL routers with firmware versions IN_1.02, SEA_1.04, and SEA_1.07. The vulnerability is due to insufficient input validation on the getpage parameter within the /cgi-bin/webproc CGI script. This flaw allows an unauthenticated remote attacker to perform path traversal attacks by supplying crafted requests, enabling arbitrary file read on the affected device.
{
"affected": [],
"aliases": [
"CVE-2025-34048"
],
"database_specific": {
"cwe_ids": [
"CWE-20",
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-06-26T16:15:28Z",
"severity": "HIGH"
},
"details": "A path traversal vulnerability exists in the web management interface of D-Link DSL-2730U, DSL-2750U, and DSL-2750E ADSL routers with firmware versions IN_1.02, SEA_1.04, and SEA_1.07. The vulnerability is due to insufficient input validation on the getpage parameter within the /cgi-bin/webproc CGI script. This flaw allows an unauthenticated remote attacker to perform path traversal attacks by supplying crafted requests, enabling arbitrary file read on the affected device.",
"id": "GHSA-4m2v-gmf9-56qj",
"modified": "2025-06-26T18:31:28Z",
"published": "2025-06-26T18:31:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-34048"
},
{
"type": "WEB",
"url": "https://github.com/threat9/routersploit/blob/master/routersploit/modules/exploits/routers/dlink/dsl_2730_2750_path_traversal.py"
},
{
"type": "WEB",
"url": "https://vulncheck.com/advisories/dlink-dsl-routers-path-traversal-file-read"
},
{
"type": "WEB",
"url": "https://www.dlink.com"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/40735"
}
],
"schema_version": "1.4.0",
"severity": [
{
"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-4M36-5V2M-V77Q
Vulnerability from github – Published: 2025-08-05 21:31 – Updated: 2025-09-23 21:30ClanSphere 2011.3 is vulnerable to a local file inclusion (LFI) flaw due to improper handling of the cs_lang cookie parameter. The application fails to sanitize user-supplied input, allowing attackers to traverse directories and read arbitrary files outside the web root. The vulnerability is further exacerbated by null byte injection (%00) to bypass file extension checks.
{
"affected": [],
"aliases": [
"CVE-2012-10034"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-05T20:15:34Z",
"severity": "HIGH"
},
"details": "ClanSphere 2011.3 is vulnerable to a local file inclusion (LFI) flaw due to improper handling of the cs_lang cookie parameter. The application fails to sanitize user-supplied input, allowing attackers to traverse directories and read arbitrary files outside the web root. The vulnerability is further exacerbated by null byte injection (%00) to bypass file extension checks.",
"id": "GHSA-4m36-5v2m-v77q",
"modified": "2025-09-23T21:30:54Z",
"published": "2025-08-05T21:31:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-10034"
},
{
"type": "WEB",
"url": "https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/auxiliary/scanner/http/clansphere_traversal.rb"
},
{
"type": "WEB",
"url": "https://sourceforge.net/projects/clansphere"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/22181"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/clansphere-local-file-inclusion-via-cookie"
}
],
"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"
},
{
"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-4M3X-CFC5-6CCG
Vulnerability from github – Published: 2026-05-13 18:30 – Updated: 2026-05-13 18:30A directory traversal vulnerability exists in BIG-IP SSL Orchestrator that allows an authenticated attacker with high privilege to overwrite, delete or corrupt arbitrary local files. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
{
"affected": [],
"aliases": [
"CVE-2026-42780"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-13T16:16:48Z",
"severity": "MODERATE"
},
"details": "A directory traversal vulnerability exists in BIG-IP SSL Orchestrator that allows an authenticated attacker with high privilege to overwrite, delete or corrupt arbitrary local files.\n\u00a0Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.",
"id": "GHSA-4m3x-cfc5-6ccg",
"modified": "2026-05-13T18:30:56Z",
"published": "2026-05-13T18:30:56Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42780"
},
{
"type": "WEB",
"url": "https://my.f5.com/manage/s/article/K000149743"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/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-4M64-G8R6-3GHW
Vulnerability from github – Published: 2025-11-13 00:30 – Updated: 2025-11-13 00:30Longjing Technology BEMS API versions up to and including 1.21 contains an unauthenticated arbitrary file download vulnerability in the 'downloads' endpoint. The 'fileName' parameter is not properly sanitized, allowing attackers to craft traversal sequences and access sensitive files outside the intended directory.
{
"affected": [],
"aliases": [
"CVE-2021-4463"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-11-12T22:15:41Z",
"severity": "HIGH"
},
"details": "Longjing Technology BEMS API versions up to and including 1.21 contains an unauthenticated arbitrary file download vulnerability in the \u0027downloads\u0027 endpoint. The \u0027fileName\u0027 parameter is not properly sanitized, allowing attackers to craft traversal sequences and access sensitive files outside the intended directory.",
"id": "GHSA-4m64-g8r6-3ghw",
"modified": "2025-11-13T00:30:17Z",
"published": "2025-11-13T00:30:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-4463"
},
{
"type": "WEB",
"url": "https://cxsecurity.com/issue/WLB-2021070173"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/206477"
},
{
"type": "WEB",
"url": "https://packetstormsecurity.com/files/163702"
},
{
"type": "WEB",
"url": "https://web.archive.org/web/20220527162453/http://www.ljkj2012.com"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/50163"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/longjing-technology-bems-api-remote-arbitrary-file-download"
},
{
"type": "WEB",
"url": "https://www.zeroscience.mk/en/vulnerabilities/ZSL-2021-5657.php"
}
],
"schema_version": "1.4.0",
"severity": [
{
"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-4M75-CR73-V7HW
Vulnerability from github – Published: 2022-09-23 00:00 – Updated: 2022-09-25 00:00ZZCMS 2022 was discovered to contain a full path disclosure vulnerability via the page /admin/index.PHP? _server.
{
"affected": [],
"aliases": [
"CVE-2022-40444"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-09-22T14:15:00Z",
"severity": "MODERATE"
},
"details": "ZZCMS 2022 was discovered to contain a full path disclosure vulnerability via the page /admin/index.PHP? _server.",
"id": "GHSA-4m75-cr73-v7hw",
"modified": "2022-09-25T00:00:19Z",
"published": "2022-09-23T00:00:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-40444"
},
{
"type": "WEB",
"url": "https://github.com/liong007/ZZCMS/issues/2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
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.