GSD-2022-25377
Vulnerability from gsd - Updated: 2023-12-13 01:19Details
The ACME-challenge endpoint in Appwrite 0.5.0 through 0.12.x before 0.12.2 allows remote attackers to read arbitrary local files via ../ directory traversal. In order to be vulnerable, APP_STORAGE_CERTIFICATES/.well-known/acme-challenge must exist on disk. (This pathname is automatically created if the user chooses to install Let's Encrypt certificates via Appwrite.)
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2022-25377",
"id": "GSD-2022-25377"
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"aliases": [
"CVE-2022-25377"
],
"details": "The ACME-challenge endpoint in Appwrite 0.5.0 through 0.12.x before 0.12.2 allows remote attackers to read arbitrary local files via ../ directory traversal. In order to be vulnerable, APP_STORAGE_CERTIFICATES/.well-known/acme-challenge must exist on disk. (This pathname is automatically created if the user chooses to install Let\u0027s Encrypt certificates via Appwrite.)",
"id": "GSD-2022-25377",
"modified": "2023-12-13T01:19:27.378385Z",
"schema_version": "1.4.0"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2022-25377",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "n/a",
"version": {
"version_data": [
{
"version_value": "n/a"
}
]
}
}
]
},
"vendor_name": "n/a"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "The ACME-challenge endpoint in Appwrite 0.5.0 through 0.12.x before 0.12.2 allows remote attackers to read arbitrary local files via ../ directory traversal. In order to be vulnerable, APP_STORAGE_CERTIFICATES/.well-known/acme-challenge must exist on disk. (This pathname is automatically created if the user chooses to install Let\u0027s Encrypt certificates via Appwrite.)"
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "n/a"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/appwrite/appwrite/blob/0.12.0/app/controllers/general.php#L539",
"refsource": "MISC",
"url": "https://github.com/appwrite/appwrite/blob/0.12.0/app/controllers/general.php#L539"
},
{
"name": "https://github.com/appwrite/appwrite/releases/tag/0.12.2",
"refsource": "MISC",
"url": "https://github.com/appwrite/appwrite/releases/tag/0.12.2"
},
{
"name": "https://github.com/appwrite/appwrite/pull/2780",
"refsource": "MISC",
"url": "https://github.com/appwrite/appwrite/pull/2780"
},
{
"name": "https://dubell.io/unauthenticated-lfi-in-appwrite-0.5.0-0.12.1/",
"refsource": "MISC",
"url": "https://dubell.io/unauthenticated-lfi-in-appwrite-0.5.0-0.12.1/"
}
]
}
},
"nvd.nist.gov": {
"cve": {
"descriptions": [
{
"lang": "en",
"value": "The ACME-challenge endpoint in Appwrite 0.5.0 through 0.12.x before 0.12.2 allows remote attackers to read arbitrary local files via ../ directory traversal. In order to be vulnerable, APP_STORAGE_CERTIFICATES/.well-known/acme-challenge must exist on disk. (This pathname is automatically created if the user chooses to install Let\u0027s Encrypt certificates via Appwrite.)"
}
],
"id": "CVE-2022-25377",
"lastModified": "2024-02-23T02:42:54.547",
"metrics": {},
"published": "2024-02-22T22:15:47.170",
"references": [
{
"source": "cve@mitre.org",
"url": "https://dubell.io/unauthenticated-lfi-in-appwrite-0.5.0-0.12.1/"
},
{
"source": "cve@mitre.org",
"url": "https://github.com/appwrite/appwrite/blob/0.12.0/app/controllers/general.php#L539"
},
{
"source": "cve@mitre.org",
"url": "https://github.com/appwrite/appwrite/pull/2780"
},
{
"source": "cve@mitre.org",
"url": "https://github.com/appwrite/appwrite/releases/tag/0.12.2"
}
],
"sourceIdentifier": "cve@mitre.org",
"vulnStatus": "Awaiting Analysis"
}
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…