IBM i Access Buffer Overflow Code DOS CVE-2015-7422

[apparitionsec@xxxxxxxxx]

[+] Credits: John Page aka hyp3rlinx

[+] Website: hyp3rlinx.altervista.org

[+] Source:  
http://hyp3rlinx.altervista.org/advisories/IBMI-ACCESS-BUFFER-OVERFLOW-DOS.txt



Vendor:
==============
www.ibm.com



Product:
====================================================
IBM i Access for Windows
Release 7.1 of IBM i Access for Windows is affected



Vulnerability Type:
========================
Stack Buffer Overflow DOS



CVE Reference:
==============
CVE-2015-7422



Vulnerability Details:
=====================
IBM i Access for Windows vulnerable to a buffer overflow, caused by improper 
bounds checking.
A local attacker could overflow a buffer and cause the program to crash.


Remediation/Fixes
The issue can be fixed by obtaining and applying the Service Pack SI57907.

The buffer overflow vulnerability can be remediated by applying Service Pack 
SI57907.

The Service Pack is available at:
http://www-03.ibm.com/systems/power/software/i/access/windows_sp.html

Workarounds and Mitigations
None known

CVSS Base Score: 4
CVSS Temporal Score: See 
https://exchange.xforce.ibmcloud.com/vulnerabilities/107770 for the current 
score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)



Disclosure Timeline:
====================================
Vendor Notification:  May 21, 2015
November 18, 2015  : Public Disclosure



Exploitation Technique:
=======================
Local 



Severity Level:
================
Med



Description:
======================================================================
Request Method(s):          [+] local  


Vulnerable Product:         [+] IBM i Access for Windows Release 7.1


Affected Area(s):           [+] IBMI i Access



[+] Disclaimer
Permission is hereby granted for the redistribution of this advisory, provided 
that it is not altered except by reformatting it, and that due credit is given. 
Permission is explicitly given for insertion in vulnerability databases and 
similar, provided that due credit is given to the author.
The author is not responsible for any misuse of the information contained 
herein and prohibits any malicious use of all security related information or 
exploits by the author or elsewhere.

by hyp3rlinx