dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-42640

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
angular-base64-upload prior to v0.1.21 is vulnerable to unauthenticated remote code execution via demo/server.php. Exploiting this vulnerability allows an attacker to upload arbitrary content to the server, which can subsequently be accessed through demo/uploads. This leads to the execution of previously uploaded content and enables the attacker to achieve code execution on the server. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

Unrestricted file upload vulnerability in angular-base64-upload demo/server.php allows unauthenticated attackers to upload arbitrary files to demo/uploads directory, leading to remote code execution.

MitigationRemove the vulnerable demo directory entirely from production deployments, or upgrade to v0.1.21+ if the maintainer provides it; implement proper file type validation and authentication if the upload functionality is still required.

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

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
High
Availability
High

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

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. Check if demo directory exists in web root
    Search the web server document root for a 'demo' directory. Common paths include /demo, /public/demo, or /angular-base64-upload/demo. Use 'find /var/www -type d -name demo' on Linux or check your project structure.
    Affected if The demo directory exists in the web-accessible path
  2. Verify demo/server.php file exists
    Locate the server.php file within the demo directory. This is the vulnerable upload handler. Check for files like /demo/server.php or /demo/inc/server.php.
    Affected if The file demo/server.php exists and is present
  3. Check if demo/uploads directory is writable
    Inspect the demo/uploads directory permissions. Run 'ls -la' on the uploads folder to confirm write permissions for the web server user.
    Affected if The demo/uploads directory exists and is writable by the web server
  4. Confirm the upload endpoint is network-accessible
    Attempt to access the server.php via HTTP from an external perspective, or verify it responds to POST requests on your internal network. Check if the path is reachable via browser or curl.
    Affected if The endpoint at /demo/server.php is accessible over HTTP/HTTPS
  5. Determine angular-base64-upload version
    Check package.json, composer.json, or bower.json for the installed version of angular-base64-upload. Compare against the fixed version v0.1.21.
    Affected if Version is below v0.1.21 or the version cannot be determined but demo files are present

If the demo directory with server.php is present and accessible on a web server running version below v0.1.21, the system is vulnerable to unrestricted file upload.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove the vulnerable demo directory entirely from production deployments, or upgrade to v0.1.21+ if the maintainer provides it; implement proper file type validation and authentication if the upload functionality is still required.

Recommended fix High confidence

v0.1.21

  1. Identify all project dependency files (package.json, bower.json, or similar) that reference angular-base64-upload
  2. Update the version specification for angular-base64-upload to v0.1.21 or later in your dependency management file
  3. Run npm update angular-base64-upload or bower update angular-base64-upload to fetch the fixed version
  4. Verify the installed version matches v0.1.21 or later using npm list angular-base64-upload or bower list
  5. Remove the demo directory from production deployments if present, as the vulnerable server.php file is located within it
  6. Audit production environments to ensure no instances of the vulnerable demo/server.php file remain accessible

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42640 — 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-42640 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