dbcve.org
AppwriteApplication

CVE-2024-1063

HIGH · 7.5 CVSS v3.1 Published 2024-01-30
Fix available
A fix is available. Upgrade to after 1.4.13 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Appwrite <= v1.4.13 is affected by a Server-Side Request Forgery (SSRF) via the '/v1/avatars/favicon' endpoint due to an incomplete fix of CVE-2023-27159.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Appwrite versions up to v1.4.13 contain a Server-Side Request Forgery (SSRF) vulnerability in the /v1/avatars/favicon endpoint. This vulnerability represents an incomplete fix of CVE-2023-27159, likely allowing attackers to make the server perform arbitrary requests to internal services, cloud metadata endpoints, or other sensitive resources by manipulating the favicon URL parameter.

MitigationUpgrade Appwrite to a version newer than v1.4.13. If immediate upgrade is not possible, restrict access to the /v1/avatars/favicon endpoint and implement network-level controls to prevent the server from making arbitrary outbound connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AppwriteApplication
Affected:<= 1.4.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Appwrite version
    Check the running Appwrite version via the admin console, deployment configuration, Docker containers, or the /v1/account/session/avatar endpoint response headers
    Affected if The installed version is v1.4.13 or any version lower than v1.4.13 (e.g., v1.4.12, v1.4.0, earlier releases)
  2. Confirm /v1/avatars/favicon endpoint is exposed
    Send a GET request to the /v1/avatars/favicon endpoint with a test URL parameter (e.g., ?url=https://example.com) and verify it returns a response
    Affected if The endpoint is reachable and accepts requests, meaning it is enabled in the deployment
  3. Verify URL validation is insufficient
    Test the endpoint by supplying internal or cloud metadata URLs (e.g., http://169.254.169.254/latest/meta-data for AWS) as the url parameter
    Affected if The server successfully fetches and returns content from internal resources or arbitrary URLs, indicating the SSRF protection is incomplete or bypassed

You are affected if your Appwrite version is v1.4.13 or lower AND the /v1/avatars/favicon endpoint is accessible AND URL validation can be bypassed to make the server request arbitrary URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.4.13
Interim mitigation

Upgrade Appwrite to a version newer than v1.4.13. If immediate upgrade is not possible, restrict access to the /v1/avatars/favicon endpoint and implement network-level controls to prevent the server from making arbitrary outbound connections.

Recommended fix Moderate confidence

Appwrite 1.4.14 or later stable release

  1. 1. Identify all Appwrite instances running version 1.4.13 or earlier
  2. 2. Plan an upgrade to Appwrite version 1.4.14 or later, as this version addresses the incomplete SSRF fix from CVE-2023-27159
  3. 3. Before upgrading, backup all databases, configurations, and storage volumes
  4. 4. Review the Appwrite upgrade documentation for version 1.4.14 or latest stable release
  5. 5. Execute the upgrade following the official upgrade procedure
  6. 6. After upgrade, verify the '/v1/avatars/favicon' endpoint now properly validates and sanitizes URLs to prevent SSRF
  7. 7. Test that legitimate favicon retrieval still functions correctly
Caveat Review Appwrite release notes between 1.4.13 and target version for any breaking changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Appwrite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1063 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data