dbcve.org
ImpactApplication · Nokia

CVE-2021-35485

HIGH · 8.0 CVSS v3.1 Published 2026-03-03
Fix available
A fix is available. Upgrade to after 19.11.2.10-20210118042150283 or later.
See remediation →
82/100
Remediation priority · High
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
The Applications component of Nokia IMPACT version through 19.11.2.10-20210118042150283 allows an authenticated user to arbitrarily upload server-side executable files via the /ui/rest-proxy/application fileupload parameter. This can occur during the adding of a new application, or during the editing of an existing one.

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

Nokia IMPACT through version 19.11.2.10 contains an arbitrary file upload vulnerability in the Applications component. An authenticated user can upload server-side executable files via the /ui/rest-proxy/application fileupload parameter when adding or editing applications, potentially leading to remote code execution.

MitigationImplement strict whitelist-based file type validation on the server side, sanitize filenames, store uploaded files outside the webroot, and disable script execution in upload directories. Apply vendor security patches when available.

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
ImpactApplication
Affected:<= 19.11.2.10-20210118042150283

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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. Identify the Nokia IMPACT installation
    Confirm that the system runs Nokia IMPACT by checking the product name in the web interface footer, about page, or system information page
    Affected if The product is confirmed to be Nokia IMPACT
  2. Check the installed version number
    Locate the version information in the Nokia IMPACT admin interface (typically in About, System Info, or Help sections) and compare it to the affected range: versions <= 19.11.2.10-20210118042150283
    Affected if The installed version is 19.11.2.10-20210118042150283 or earlier
  3. Verify the Applications component is accessible
    Log into the Nokia IMPACT web interface and navigate to the Applications section (or check if the /ui/rest-proxy/application endpoint responds to requests)
    Affected if The Applications component is present and accessible to authenticated users
  4. Confirm file upload capability in Applications
    In the Applications section, check if the Add Application or Edit Application forms include a file upload field or attachment option
    Affected if File upload functionality exists when adding or editing applications

A system is affected if it runs Nokia IMPACT version 19.11.2.10-20210118042150283 or earlier with the Applications component and its file upload feature enabled and accessible to authenticated users.

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 19.11.2.10-20210118042150283
Interim mitigation

Implement strict whitelist-based file type validation on the server side, sanitize filenames, store uploaded files outside the webroot, and disable script execution in upload directories. Apply vendor security patches when available.

Recommended fix Moderate confidence

Nokia IMPACT version newer than 19.11.2.10-20210118042150283 (contact Nokia support for exact patched release)

  1. Contact Nokia IMPACT support or visit the official Nokia support portal to obtain the latest security-patched version of Nokia IMPACT
  2. Request specific information about the security fix for CVE-2021-35485 and confirm which version includes the patch
  3. Upgrade the Nokia IMPACT installation to the version provided by Nokia that includes the security fix
  4. After upgrade, verify that the /ui/rest-proxy/application fileupload endpoint no longer accepts executable file types
  5. Restrict file upload permissions to authenticated administrators only as an additional hardening measure
Caveat Minor: Review any custom application configurations after upgrade as file upload handling may have changed

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

Fix this in Impact 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-2021-35485 — 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-2021-35485 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