dbcve.org
UneggApplication · Unegg Project

CVE-2020-7860

HIGH · 7.8 CVSS v3.1 Published 2021-06-11
Fix available
A fix is available. Upgrade to 1.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
UnEGG v0.5 and eariler versions have a Integer overflow vulnerability, triggered when the user opens a malformed specific file that is mishandled by UnEGG. Attackers could exploit this and arbitrary code execution. This issue affects: Estsoft UnEGG 0.5 versions prior to 1.0 on linux.

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 confidence

UnEGG v0.5 and earlier contains an integer overflow vulnerability in file parsing that can be triggered by opening a malformed specific file, potentially allowing arbitrary code execution.

MitigationUpgrade to UnEGG version 1.0 or later which contains the fix for the integer overflow vulnerability in file handling.

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
UneggApplication
Affected:>= 0.5, < 1.0

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Verify UnEGG is installed
    Check for the presence of the UnEGG executable or library on the system (common paths: /usr/bin/unegg, /usr/local/bin/unegg, or check package manager listings)
    Affected if UnEGG executable or package is found on the system
  2. Determine installed UnEGG version
    Run 'unegg --version' or check the package manager (dpkg -l unegg, rpm -qi unegg) to retrieve the installed version number
    Affected if Version is 0.5 or any version lower than 1.0 (e.g., 0.4, 0.3, etc.)
  3. Confirm file parsing functionality is in use
    Identify whether UnEGG is actively used or configured to parse project/input files (check for project files, config files referencing UnEGG, or recent file processing activity)
    Affected if UnEGG is configured to parse files from untrusted or external sources
  4. Check for malformed input files
    Inspect recent or queued input files for signs of corruption, unusual size, or malformed structure that could trigger the integer overflow during parsing
    Affected if Malformed files matching the vulnerable file format are present and have been processed

The environment is affected if UnEGG version 0.5 or any version below 1.0 is installed and is being used to parse files, since the integer overflow vulnerability exists in the file parsing component of these versions.

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
Upgrade available Upgrade to 1.0 or later
Fixed in 1.0
Interim mitigation

Upgrade to UnEGG version 1.0 or later which contains the fix for the integer overflow vulnerability in file handling.

Fix this in Unegg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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