dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2024-13206

HIGH · 7.8 CVSS v3.1 Published 2025-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A vulnerability classified as critical has been found in REVE Antivirus 1.0.0.0 on Linux. This affects an unknown part of the file /usr/local/reveantivirus/tmp/reveinstall. The manipulation leads to incorrect default permissions. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

REVE Antivirus 1.0.0.0 for Linux ships with the installation script /usr/local/reveantivirus/tmp/reveinstall having insecure default permissions, allowing local unprivileged users to potentially modify or overwrite this file. This could enable local privilege escalation if the file is executed with elevated privileges during installation or maintenance operations.

MitigationCorrect file permissions on /usr/local/reveantivirus/tmp/reveinstall to remove world/group write access (e.g., chmod 755 or stricter ownership). If the software vendor does not provide a patch, evaluate whether the product meets your security requirements or consider alternative solutions.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Check if REVE Antivirus is installed
    ls -la /usr/local/reveantivirus/ 2>/dev/null || echo 'Not installed'
    Affected if The /usr/local/reveantivirus directory does not exist, so the product is not installed and this CVE does not apply
  2. Verify the vulnerable file exists
    ls -la /usr/local/reveantivirus/tmp/reveinstall 2>/dev/null
    Affected if The file /usr/local/reveantivirus/tmp/reveinstall exists on the system
  3. Inspect file permissions for world/group write access
    stat -c '%a %A' /usr/local/reveantivirus/tmp/reveinstall 2>/dev/null
    Affected if Permissions show '2' in the world position (e.g., 777, 776, 667, 666) or '2' in the group position (e.g., 775, 774, 665, 664) indicating world or group write access
  4. Check file ownership and group
    stat -c '%U:%G' /usr/local/reveantivirus/tmp/reveinstall 2>/dev/null
    Affected if File is owned by root but is writable by a non-root user or group, or file is owned by a non-root user allowing modification by other users

You are affected if REVE Antivirus 1.0.0.0 for Linux is installed and the file /usr/local/reveantivirus/tmp/reveinstall has world-writable or group-writable permissions that allow unprivileged users to modify it.

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

Correct file permissions on /usr/local/reveantivirus/tmp/reveinstall to remove world/group write access (e.g., chmod 755 or stricter ownership). If the software vendor does not provide a patch, evaluate whether the product meets your security requirements or consider alternative solutions.

Recommended fix Low confidence
  1. Audit the file /usr/local/reveantivirus/tmp/reveinstall and determine if it is required for the antivirus functionality
  2. If the file is not essential, remove it: rm /usr/local/reveantivirus/tmp/reveinstall
  3. If the file is required, inspect its current permissions using: ls -la /usr/local/reveantivirus/tmp/reveinstall
  4. Change file ownership to root:root if possible: chown root:root /usr/local/reveantivirus/tmp/reveinstall
  5. Restrict file permissions to prevent unauthorized access: chmod 600 /usr/local/reveantivirus/tmp/reveinstall
  6. Verify the changes: ls -la /usr/local/reveantivirus/tmp/reveinstall
  7. Review parent directory /usr/local/reveantivirus/tmp/ for similar permission issues and apply consistent restrictions
  8. Consider replacing REVE Antivirus with an actively maintained security solution if no response from vendor
Caveat No clear upgrade path available - vendor did not respond to disclosure and no fixed version is documented

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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