CVE-2016-1239
First published: Sat Feb 19 2022(Updated: )
duck before 0.10 did not properly handle loading of untrusted code from the current directory.
Credit: security@debian.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Debian Duck | <0.10 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-1239?
CVE-2016-1239 is classified as a medium severity vulnerability due to its potential for code execution from untrusted sources.
How do I fix CVE-2016-1239?
To fix CVE-2016-1239, upgrade Duck to version 0.10 or later.
What software is affected by CVE-2016-1239?
CVE-2016-1239 affects Duck versions prior to 0.10, specifically in Debian systems.
Can CVE-2016-1239 lead to remote code execution?
Yes, CVE-2016-1239 can lead to remote code execution if untrusted code is loaded from the current directory.
Who is responsible for patching CVE-2016-1239?
The responsibility for patching CVE-2016-1239 lies with the software maintainers and users of the affected versions.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/remedy
- agent/references
- agent/severity
- agent/author
- agent/description
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- vendor/debian
- canonical/debian duck