full-disclosure - Re: MS13-102: NtConnectPort() LPC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Fri, 20 Dec 2013 06:36:50 +0000
From: yuange <yuange1975@...mail.com>
To: Rhys Kidd <rhyskidd@...il.com>
Cc: full-disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: MS13-102: NtConnectPort() LPC

1. Impersonate the server
2. you can use com's callback , ConnectionPoint.

Date: Sun, 15 Dec 2013 03:16:02 +1100
Subject: MS13-102: NtConnectPort() LPC
From: rhyskidd@...il.com
To: yuanrenguang@....cn; yuange1975@...mail.com; yuange1975@....com

Hi Yuan,
Good find for the NtConnectPort() MaximumMessageLength overflow. LPC has had many bugs and issues when >256 bytes.
Can you tell me which LPC "RPC Control" PortName you found best to imitate as a server so as to trigger the stack overflow?

Is it one of these? http://lists.grok.org.uk/pipermail/full-disclosure/2010-October/076830.html

Best
---
Xǐ yuán,
Shànyú fāxiàn de NtConnectPort ( ) MaximumMessageLength yìchū. LPC yǒuguò xǔduō cuòwù hé wèntí shí, > 256 zì jié.
Nǐ néng gàosu wǒ zhè LPC “RPC Control” nǐ zhǎodào zuì hǎo de mófǎng zuòwéi fúwùqì, cóng'ér chùfā zhàn yìchū duānkǒu míngchēng?
Shì bùshì qízhōng zhī yī? Http://Lists.Grok.Org.Uk/pipermail/full-disclosure/2010-October/076830.Html
Zuì hǎo de

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/