CVE-2014-125025: FFmpeg decode_pulses memory corruption
First published: Sun Jun 19 2022(Updated: )
A vulnerability classified as problematic has been found in FFmpeg 2.0. This affects the function decode_pulses. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. It is recommended to apply a patch to fix this issue.
Credit: cna@vuldb.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| FFmpeg | =2.0 |
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-2014-125025?
The severity of CVE-2014-125025 is medium with a severity value of 5.5.
How does CVE-2014-125025 affect FFmpeg 2.0?
CVE-2014-125025 affects FFmpeg 2.0 through the function decode_pulses, leading to memory corruption.
Can CVE-2014-125025 be exploited remotely?
Yes, CVE-2014-125025 can be initiated remotely.
Is there a patch available to fix CVE-2014-125025?
Yes, it is recommended to apply a patch to fix CVE-2014-125025.
Where can I find more information about CVE-2014-125025?
You can find more information about CVE-2014-125025 in the references: http://git.videolan.org/?p=ffmpeg.git;a=commit;h=6e42ccb9db and https://vuldb.com/?id.12303.
- agent/type
- agent/author
- agent/remedy
- agent/weakness
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/title
- agent/references
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/ffmpeg
- canonical/ffmpeg
- version/ffmpeg/2.0