dbcve.org
RlottieApplication · Samsung

CVE-2025-53075

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-30
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Input Validation vulnerability in Samsung Open Source rLottie allows Path Traversal.This issue affects rLottie: V0.2.

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

An improper input validation vulnerability in Samsung's rLottie library version V0.2 allows path traversal attacks. The vulnerability stems from insufficient validation of file paths when processing Lottie animation files, potentially enabling attackers to access files outside the intended directory through specially crafted file paths containing '..' sequences.

MitigationUpgrade rLottie to a patched version that implements proper path sanitization and canonicalization. If no patch is available, implement application-level input validation to reject paths containing traversal sequences before passing files to the library.

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
RlottieApplication
Affected:= 0.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 rLottie library presence
    Search for the rLottie library file (librlottie.so on Linux, rlottie.dll on Windows, or librlottie.dylib on macOS) in the application directory or system library paths. If the application is mobile-based, check the app's bundled libraries.
    Affected if The library is found and is being used by the application.
  2. Determine rLottie version
    Check the version information of the identified rLottie library file. On Linux/macOS, use 'strings librlottie.so | grep -i version' or check the file metadata. On Windows, right-click the DLL and select Properties > Details. Alternatively, check the application's dependency list or build configuration if available.
    Affected if The version is exactly V0.2.
  3. Verify Lottie file processing is active
    Review the application code or configuration to confirm it uses rLottie to parse and render Lottie animation files (.json files). Check for imports of rLottie headers (rlottie.h) or dynamic loading of the library for animation rendering purposes.
    Affected if The application processes Lottie animation files using rLottie.
  4. Assess file input source
    Determine whether the application accepts Lottie files from untrusted sources such as user uploads, network requests, or external storage. Check if there is any input validation or sanitization on file paths passed to rLottie before processing.
    Affected if Lottie files from untrusted sources are processed without validation on file path components.

You are affected if rLottie version 0.2 is in use AND your application processes Lottie animation files, particularly from untrusted sources, without validating path components for traversal sequences before passing them to the library.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade rLottie to a patched version that implements proper path sanitization and canonicalization. If no patch is available, implement application-level input validation to reject paths containing traversal sequences before passing files to the library.

Recommended fix Moderate confidence
  1. Review the vulnerability details in the PR to understand the path traversal issue
  2. Clone or fetch the latest rLottie repository
  3. Apply the changes from pull request #571 (https://github.com/Samsung/rlottie/pull/571) to your local copy of rLottie version 0.2
  4. Verify the patch applies cleanly and compiles without errors
  5. Rebuild your application with the patched rLottie library
  6. Test the fix by attempting file load operations with paths containing traversal sequences (e.g., '../') to confirm the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rlottie Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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