CVE-2017-13179

In the ihevcd_allocate_static_bufs and ihevcd_create functions of SoftHEVC, there is a possible out-of-bounds write due to a use after free

published January 12, 2018

CVSS
β€”
EPSS
2%
Percentile
83.6
In the wild
Unconfirmed
What it is

🚨 A sneaky out-of-bounds write hides in the SoftHEVC code, reminiscent of a reserved hotel room that was rented out without telling the guest β€” an unexpected surprise for anyone! 😱 This vulnerability is like a hotel manager failing to inform you that the room you booked is no longer available; instead, they just give your key to someone else. In this scenario, the memory management in SoftHEVC allows for a dangerous overlap, where a freed space is still accessible, creating a risky situation. An attacker could potentially execute remote code as a privileged process, which could lead to serious disruptions or even full control of the device. Think of it as someone completely taking over your hotel room and holding the guests hostage until their demands are met! This is a scenario you definitely want to avoid.

Put simply

This vulnerability is like a hotel manager failing to inform you that the room you booked is no longer available; instead, they just give your key to someone else. In this scenario, the memory management in SoftHEVC allows for a dangerous overlap, where a freed space is still accessible, creating a risky situation. The vulnerability arises from a use-after-free condition in the ihevcd_allocate_static_bufs and ihevcd_create functions, where both ps_codec_obj and ps_create_op->s_ivd_create_op_t.pv_handle point to the same memory. When ps_codec_obj is freed, the pointer still holds the same address, allowing unintended write access.

What to do

An attacker could potentially execute remote code as a privileged process, which could lead to serious disruptions or even full control of the device. Think of it as someone completely taking over your hotel room and holding the guests hostage until their demands are met! This is a scenario you definitely want to avoid. To patch this, it’s crucial to update to the latest version of SoftHEVC that fixes this issue. Additionally, conduct a thorough review of memory management in your code and implement proper checks to clear references after freeing memory. Keep your application secured! You've got this! With the right updates, your app will be safer in no time! πŸ›‘οΈ

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.02352 Β· 83.6th percentile
Published
2018-01-12T23:00Z
EPSS history
Timeline
  • 12 JAN 23:00Z
    In the ihevcd_allocate_static_bufs and ihevcd_create functions of SoftHEVC, there is a possible out-of-bounds write due to a use after free
    cvelistv5