dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-55504

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
An issue in RAR Extractor - Unarchiver Free and Pro v.6.4.0 allows local attackers to inject arbitrary code potentially leading to remote control and unauthorized access to sensitive user data via the exploit_combined.dylib component on MacOS.

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

A code injection vulnerability exists in the exploit_combined.dylib component of RAR Extractor - Unarchiver (Free and Pro) v6.4.0 on macOS. Local attackers can inject arbitrary code through this library component, potentially achieving unauthorized access to sensitive user data.

MitigationApply vendor-supplied patch/update to v6.4.0 when available; until then, restrict local untrusted user access and exercise caution when processing untrusted archive files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 if RAR Extractor - Unarchiver is installed
    Check /Applications folder or Spotlight search for 'RAR Extractor' or 'Unarchiver' applications. Run: ls -la /Applications | grep -i 'rar\|unarchiver'
    Affected if The application (Free or Pro version) is found in the system
  2. Determine the installed version of RAR Extractor - Unarchiver
    Right-click the application in /Applications, select 'Get Info', or run: mdls -name kCFBundleVersionString '/path/to/RAR Extractor.app' (adjust path as needed). Compare the version number to v6.4.0
    Affected if The installed version is exactly v6.4.0
  3. Locate the exploit_combined.dylib component
    Navigate to the application bundle contents: right-click the .app file, select 'Show Package Contents', then check Contents/Frameworks or Contents/MacOS for exploit_combined.dylib. Alternatively, run: find '/Applications/RAR Extractor.app' -name 'exploit_combined.dylib'
    Affected if The file exploit_combined.dylib exists within the application bundle
  4. Verify file permissions on the dylib
    Run: ls -la '/Applications/RAR Extractor.app/Contents/Frameworks/exploit_combined.dylib' (adjust path if the file is in a different location). Check if the file is writable by non-privileged users or if it has been modified
    Affected if The dylib is writable by standard users or shows unexpected modification timestamps indicating potential injection

A user is affected if RAR Extractor - Unarchiver v6.4.0 is installed with the exploit_combined.dylib component present and accessible for modification by local attackers.

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

Apply vendor-supplied patch/update to v6.4.0 when available; until then, restrict local untrusted user access and exercise caution when processing untrusted archive files.

Have this fixed 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 help mitigating

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-2024-55504 — 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-2024-55504 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