dbcve.org
GurunaviApplication

CVE-2021-20693

HIGH · 7.5 CVSS v3.1 Published 2021-04-26
Fix available
A fix is available. Upgrade to after 11.1.2 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
Improper access control vulnerability in Gurunavi App for Android ver.10.0.10 and earlier and for iOS ver.11.1.2 and earlier allows a remote attacker to lead a user to access an arbitrary website via the vulnerable App.

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

Improper access control in Gurunavi mobile app allows remote attackers to redirect users to arbitrary websites. The app likely fails to properly validate or sanitize URLs before navigating to them, enabling an open redirect attack through the application's interface.

MitigationUsers should update Gurunavi App to the latest version (Android >10.0.10, iOS >11.1.2). Developers should implement proper URL validation and whitelist-based URL handling to prevent unauthorized redirects.

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
GurunaviApplication
Affected:<= 10.0.10<= 11.1.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check installed Android Gurunavi app version
    Open Android device Settings > Apps > Gurunavi (or find in app drawer, tap App info) and view the Version number displayed under App info or in the app store listing
    Affected if Version shown is 10.0.10 or lower
  2. Check installed iOS Gurunavi app version
    Open iOS device Settings > General > iPhone Storage > Gurunavi (or open App Store, tap profile icon, view purchased apps) and locate the version number
    Affected if Version shown is 11.1.2 or lower
  3. Verify current installed version against affected ranges
    If you cannot view the exact version number, open the Gurunavi app and navigate to Settings > Help/About to find the precise version string
    Affected if Any Android version <= 10.0.10 or any iOS version <= 11.1.2 is installed

The environment is affected if the Gurunavi mobile app is installed with Android version 10.0.10 or earlier, or iOS version 11.1.2 or earlier.

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 11.1.2
Interim mitigation

Users should update Gurunavi App to the latest version (Android >10.0.10, iOS >11.1.2). Developers should implement proper URL validation and whitelist-based URL handling to prevent unauthorized redirects.

Fix this in Gurunavi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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