dbcve.org
SafeApplication · F Secure

CVE-2022-38164

MEDIUM · 6.5 CVSS v3.1 Published 2022-11-07
Fix available
A fix is available. Upgrade to after 19.0 or later.
See remediation →
72/100
Remediation priority · Elevated
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 vulnerability affecting F-Secure SAFE browser for Android and iOS was discovered. A maliciously crafted website could make a phishing attack with URL spoofing as the browser only display certain part of the entire URL.

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 · moderate confidence

The F-Secure SAFE browser for Android and iOS has a URL spoofing vulnerability where it only displays a portion of the URL in the address bar. This allows malicious websites to conceal their true destination, making phishing attacks appear legitimate.

MitigationUsers should update F-Secure SAFE to the latest patched version when released by the vendor and remain vigilant about URL legitimacy until the update is applied.

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
SafeApplication
Affected:<= 19.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 F-Secure SAFE application version on device
    Open the device settings, navigate to Apps or Application Manager, locate F-Secure SAFE, and view the version information displayed
    Affected if The version listed is 19.0 or lower
  2. Verify version via app store or installed package
    Check the app version in Google Play Store (Android) or App Store (iOS) entry for F-Secure SAFE, or check the package details in device settings
    Affected if The displayed version number is 19.0 or below
  3. Compare version to affected range
    Review the confirmed version number against the affected range of version 19.0 and below
    Affected if The installed version is 19.0 or any version number lower than 19.0
  4. Test URL display behavior in SAFE browser
    Open F-Secure SAFE browser and navigate to a website with a long URL. Observe whether the address bar shows the full URL or truncates/hides portions of it
    Affected if The browser address bar displays only a partial URL and conceals portions of the domain or path

A user is affected if F-Secure SAFE version 19.0 or lower is installed AND the browser feature displays incomplete URLs in the address bar

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.0
Interim mitigation

Users should update F-Secure SAFE to the latest patched version when released by the vendor and remain vigilant about URL legitimacy until the update is applied.

Fix this in Safe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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