| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Powerproduction StoryBoard Quick 6.0 and classified as critical. Affected by this issue is some unknown functionality. The manipulation leads to memory corruption. This vulnerability is documented as CVE-2011-5172. Additionally, an exploit exists.
Details
A vulnerability was found in Powerproduction StoryBoard Quick 6.0 (Forum Software). It has been rated as very critical. This issue affects an unknown part. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Stack-based buffer overflow in StoryBoard Quick 6 Build 3786, and possibly StoryBoard Artist and StoryBoard Studio, allows remote attackers to execute arbitrary code via a long string in the string element field in a frame xml file.
The weakness was released 09/15/2012 (Website). The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2011-5172 since 09/15/2012. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/05/2025).
The exploit is available at exploit-db.com. It is declared as functional.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (71574), Exploit-DB (18186), SecurityFocus (BID 50853†), OSVDB (77421†) and Secunia (SA47045†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.4
VulDB Base Score: 10.0
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Functional
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/01/2011 🔍09/15/2012 🔍
09/15/2012 🔍
09/15/2012 🔍
03/24/2015 🔍
05/05/2025 🔍
Sources
Advisory: exploit-db.comStatus: Not defined
CVE: CVE-2011-5172 (🔍)
GCVE (CVE): GCVE-0-2011-5172
GCVE (VulDB): GCVE-100-62261
X-Force: 71574 - StoryBoard Quick XML buffer overflow
SecurityFocus: 50853
Secunia: 47045 - StoryBoard Quick Frame File Parsing Buffer Overflow Vulnerability, Highly Critical
OSVDB: 77421
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/24/2015 12:22Updated: 05/05/2025 04:14
Changes: 03/24/2015 12:22 (52), 02/07/2018 07:45 (7), 05/05/2025 04:14 (15)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.