TizenOperating system · Linux
CVE-2021-25433
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 · uneditedImproper authorization vulnerability in Tizen factory reset policy prior to Firmware update JUL-2021 Release allows untrusted applications to perform factory reset using dbus signal.
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 confidenceImproper authorization in Tizen's factory reset policy allows untrusted applications to trigger factory reset via dbus signal. The vulnerability exists in the dbus interface handling for factory reset, where authorization checks are insufficient or missing before the JUL-2021 firmware update.
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
TizenOperating system
< 5.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Tizen versionCheck the installed Tizen firmware version using 'getprop ro.build.version.tizen' or check /etc/os-release for the Tizen version entryAffected if Version is below 5.5 (e.g., 5.0, 5.5 M1, etc.)
-
Verify dbus factory reset interface existsList dbus service configuration files related to factory reset in /etc/dbus-1/system.d/ or /usr/share/dbus-1/system-services/ and check for a factory reset service fileAffected if A dbus service file for factory reset exists and is present on the system
-
Inspect dbus policy for factory reset serviceExamine the XML policy configuration in the factory reset dbus service file for <allow> rules without proper sender authentication or that lack <deny> rules for untrusted callersAffected if The policy contains <allow> rules without requiring specific sender match or lacks proper <deny> rules blocking untrusted applications
-
Check for missing authorization enforcementReview the dbus service configuration to verify if authorization checks are enforced before factory reset is triggered - look for missing 'org.freedesktop.DBus' checks or absent method call validationAffected if The dbus interface configuration allows any application to send the factory reset signal without authentication or authorization constraints
The system is affected if running Tizen version below 5.5 AND the factory reset dbus interface is exposed with insufficient or missing authorization checks in its configuration.
Generated from the published advisory. Verify against your own configuration.
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 data5.5
Apply the JUL-2021 firmware update to Tizen devices to receive the patched factory reset policy with proper authorization checks for dbus signals.
Fix this in Tizen
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2021-25433 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-25433 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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