FKIE_CVE-2022-25377
Vulnerability from fkie_nvd - Published: 2024-02-22 22:15 - Updated: 2025-04-03 13:17
Severity ?
Summary
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.)
References
{
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:appwrite:appwrite:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E5B08D8C-5305-4B0A-8CDF-644AE6D40485",
"versionEndExcluding": "0.12.2",
"versionStartIncluding": "0.5.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"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.)"
},
{
"lang": "es",
"value": "El endpoint del desaf\u00edo ACME en Appwrite v0.5.0 hasta v0.12.x anterior a v0.12.2 permite a atacantes remotos leer archivos locales de su elecci\u00f3n a trav\u00e9s del directory traversal ../. Para ser vulnerable, APP_STORAGE_CERTIFICATES/.well-known/acme-challenge debe existir en el disco. (Este nombre de ruta se crea autom\u00e1ticamente si el usuario elige instalar los certificados Let\u0027s Encrypt a trav\u00e9s de Appwrite)."
}
],
"id": "CVE-2022-25377",
"lastModified": "2025-04-03T13:17:44.300",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
},
"published": "2024-02-22T22:15:47.170",
"references": [
{
"source": "cve@mitre.org",
"tags": [
"Exploit"
],
"url": "https://dubell.io/unauthenticated-lfi-in-appwrite-0.5.0-0.12.1/"
},
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/appwrite/appwrite/blob/0.12.0/app/controllers/general.php#L539"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/appwrite/appwrite/pull/2780"
},
{
"source": "cve@mitre.org",
"tags": [
"Release Notes"
],
"url": "https://github.com/appwrite/appwrite/releases/tag/0.12.2"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit"
],
"url": "https://dubell.io/unauthenticated-lfi-in-appwrite-0.5.0-0.12.1/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/appwrite/appwrite/blob/0.12.0/app/controllers/general.php#L539"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/appwrite/appwrite/pull/2780"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes"
],
"url": "https://github.com/appwrite/appwrite/releases/tag/0.12.2"
}
],
"sourceIdentifier": "cve@mitre.org",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-22"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
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…