- Comment
- Impact
- Per: http://technet.microsoft.com/en-us/security/bulletin/ms12-039
AV:N per "How could an attacker exploit the vulnerability?
An attacker could convince a user to open a legitimate Microsoft Lync related file (such as an .ocsmeet file) that is located in the same network directory as a specially crafted dynamic link library (DLL) file. Then, while opening the legitimate file, Microsoft Lync could attempt to load the DLL file and execute any code it contained.
In an email attack scenario, an attacker could exploit the vulnerability by sending a legitimate Microsoft Lync-related file (such as an .ocsmeet file) to a user, and convincing the user to place the attachment into a directory that contains a specially crafted DLL file and to open the legitimate file. Then, while opening the legitimate file, Microsoft Lync could attempt to load the DLL file and execute any code it contained.
In a network attack scenario, an attacker could place a legitimate Microsoft Lync-related file and a specially crafted DLL in a network share, a UNC, or WebDAV location and then convince the user to open the file."
- Solution
- Per: http://technet.microsoft.com/en-us/security/bulletin/ms12-039
AV:N per "How could an attacker exploit the vulnerability?
An attacker could convince a user to open a legitimate Microsoft Lync related file (such as an .ocsmeet file) that is located in the same network directory as a specially crafted dynamic link library (DLL) file. Then, while opening the legitimate file, Microsoft Lync could attempt to load the DLL file and execute any code it contained.
In an email attack scenario, an attacker could exploit the vulnerability by sending a legitimate Microsoft Lync-related file (such as an .ocsmeet file) to a user, and convincing the user to place the attachment into a directory that contains a specially crafted DLL file and to open the legitimate file. Then, while opening the legitimate file, Microsoft Lync could attempt to load the DLL file and execute any code it contained.
In a network attack scenario, an attacker could place a legitimate Microsoft Lync-related file and a specially crafted DLL in a network share, a UNC, or WebDAV location and then convince the user to open the file."
[
{
"nodes": [
{
"negate": false,
"cpeMatch": [
{
"criteria": "cpe:2.3:a:microsoft:lync:2010:*:attendant_x64:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "FD4AAE75-E507-4EE5-926E-630D6C0B4B90"
},
{
"criteria": "cpe:2.3:a:microsoft:lync:2010:*:attendant_x86:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "20722891-B55F-42C1-9DCF-34196A9932A5"
},
{
"criteria": "cpe:2.3:a:microsoft:lync:2010:*:attendee:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "EE98CEE9-200B-494A-B645-D14ACB577250"
},
{
"criteria": "cpe:2.3:a:microsoft:lync:2010:*:x64:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "AF2C62AD-CC37-42B4-88AD-75F8F603ADEB"
},
{
"criteria": "cpe:2.3:a:microsoft:lync:2010:*:x86:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "F01B787D-6263-4753-977D-211432447E38"
}
],
"operator": "OR"
}
]
}
]