dbcve.org
Impact MobileApplication · Nokia

CVE-2021-35486

HIGH · 8.1 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 →
88/100
Remediation priority · High
Remotely reachable No privileges

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
A Cross-Site Request Forgery (CSRF) vulnerability in Nokia IMPACT through 19.11.2.10-20210118042150283 allows a remote attacker to import and overwrite the entire application configuration. Specifically, in /ui/rest-proxy/entity/import, neither the X-CSRF-NONCE HTTP header nor the CSRF-NONCE cookie is validated.

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 versions through 19.11.2.10 contain a CSRF vulnerability in the /ui/rest-proxy/entity/import endpoint where neither the X-CSRF-NONCE HTTP header nor the CSRF-NONCE cookie is validated, allowing remote attackers to trick authenticated users into importing and overwriting the entire application configuration.

MitigationImplement and enforce CSRF token validation by requiring and verifying both the X-CSRF-NONCE header and CSRF-NONCE cookie on the import endpoint, following the same validation pattern used elsewhere in the application.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 Nokia IMPACT installation and version
    Check the product version in the Nokia IMPACT administrative interface or system information page. Look for version numbers in the format 19.11.x.x or confirm the exact build number.
    Affected if The installed version is 19.11.2.10 or any earlier version (versions through 19.11.2.10-20210118042150283 are affected)
  2. Confirm the /ui/rest-proxy/entity/import endpoint exists
    Access the Nokia IMPACT web interface and navigate to the configuration import functionality, or verify the presence of this REST endpoint through API documentation or network traffic analysis.
    Affected if The /ui/rest-proxy/entity/import endpoint is accessible in the deployment
  3. Test for missing X-CSRF-NONCE header validation
    Send a POST request to /ui/rest-proxy/entity/import without the X-CSRF-NONCE header and observe if the request is accepted. Use a tool like curl or Burp Suite to remove the header and check the response.
    Affected if The endpoint accepts requests without the X-CSRF-NONCE header (vulnerable condition)
  4. Test for missing CSRF-NONCE cookie validation
    Send a POST request to /ui/rest-proxy/entity/import without the CSRF-NONCE cookie and observe if the request is accepted. Compare behavior with requests that include a valid CSRF-NONCE cookie.
    Affected if The endpoint accepts requests without the CSRF-NONCE cookie (vulnerable condition)
  5. Compare CSRF protection on other endpoints
    Test other endpoints in the IMPACT application that do enforce CSRF protection (if known). Verify whether they require both X-CSRF-NONCE header and CSRF-NONCE cookie, and confirm the import endpoint does not enforce the same requirements.
    Affected if Other endpoints enforce CSRF tokens but /ui/rest-proxy/entity/import does not (confirms the specific vulnerability)

A user is affected if they are running Nokia IMPACT version 19.11.2.10 or earlier AND the /ui/rest-proxy/entity/import endpoint accepts requests without validating both the X-CSRF-NONCE header and the CSRF-NONCE cookie.

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.

From vendor data
Upgrade available Upgrade to a release after 19.11.2.10-20210118042150283
Interim mitigation

Implement and enforce CSRF token validation by requiring and verifying both the X-CSRF-NONCE header and CSRF-NONCE cookie on the import endpoint, following the same validation pattern used elsewhere in the application.

Fix this in Impact Mobile Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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