Fiori ClientApplication · Sap

CVE-2021-33699

MEDIUM · 6.5 CVSS v3.1 Published 2021-08-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Task Hijacking is a vulnerability that affects the applications running on Android devices due to a misconfiguration in their AndroidManifest.xml with their Task Control features. This allows an unauthorized attacker or malware to takeover legitimate apps and to steal user's sensitive information.

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

Task Hijacking vulnerability in Android apps caused by improper configuration of Task Control features in AndroidManifest.xml. Apps with misconfigured attributes like android:allowTaskReparenting or improper intent filter settings can have their tasks taken over by malicious applications. Attackers exploit this by hijacking the app's task to present fraudulent UIs and steal user credentials or sensitive data.

MitigationReview and correct the android:allowTaskReparenting, android:launchMode, and intent filter configurations in AndroidManifest.xml to prevent unauthorized task takeover. Set appropriate task affinities and use android:excludeFromRecents or android:noHistory where appropriate.

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
Fiori ClientApplication
Affected:= 3.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Sap Fiori Client version
    Check the installed version of Sap Fiori Client on the Android device through Settings > Apps > Sap Fiori Client, or use 'adb shell pm list packages' and 'adb shell dumpsys package <package_name>' to retrieve version info
    Affected if The installed version is exactly 3.2
  2. Examine android:allowTaskReparenting in AndroidManifest.xml
    Decompile the APK and inspect AndroidManifest.xml for android:allowTaskReparenting attributes set to true on activity elements
    Affected if android:allowTaskReparenting="true" is present without corresponding task affinity controls
  3. Review android:launchMode settings
    Decompile the APK and inspect AndroidManifest.xml activity declarations for android:launchMode attributes
    Affected if launchMode is set to singleInstance or singleTask without proper task affinity configuration
  4. Inspect intent filter configurations
    Decompile the APK and examine intent-filter elements in AndroidManifest.xml for exported status and category definitions
    Affected if Intent filters lack explicit android:exported="false" or use overly permissive category settings
  5. Check task affinity configuration
    Decompile the APK and examine android:taskAffinity attributes on activity elements in AndroidManifest.xml
    Affected if Task affinity is not defined or is set to a shared value that allows other apps to associate tasks

A user is affected if Sap Fiori Client version 3.2 is installed AND the AndroidManifest.xml contains misconfigured task control attributes (allowTaskReparenting, launchMode, or intent filters) that permit unauthorized task hijacking.

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

Review and correct the android:allowTaskReparenting, android:launchMode, and intent filter configurations in AndroidManifest.xml to prevent unauthorized task takeover. Set appropriate task affinities and use android:excludeFromRecents or android:noHistory where appropriate.

Fix this in Fiori Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-33699 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