full-disclosure - Security Bug in MSVC

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BAY19-DAV2632CEC539B48A5D07237D91D0@phx.gbl>
Date: Wed Jan 18 19:25:04 2006
From: se_cur_ity at hotmail.com (Morning Wood)
Subject: Security Bug in MSVC

> In all this, I am discounting the fact that if someone is building
> untrusted sources, (s)he is most likely going to run the untrusted
> program afterwards.

this does not run an untrusted program.
if you noted, I named it a "feature bug"
and my poc is a simple "hello world" sample

Judging from MS extensive information to me,direct from MSRC, this is an
issue.
remote code can be pulled in and executed without any
notice or warning to the user.
I am not leveraging directives for CPP ( cc is the Makefile eqiv)

MSVC tends to hide ( especially these actions ) to the end user.

cheers,
Donnie