Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outlook 2010: actual characters exposed in password fields of secue dialogs #4095

Closed
nvaccessAuto opened this issue Apr 28, 2014 · 3 comments
Closed
Labels
Milestone

Comments

@nvaccessAuto
Copy link

@nvaccessAuto nvaccessAuto commented Apr 28, 2014

Reported by mdcurran on 2014-04-28 03:04
In password fields in Outlook 2010 when ITextDocument is not available, actual characters are exposed which is obviously a security risk. Standard edit controls have already been protected against, but richEdit controls (no ITextDocument) have not. _getTextRange on the Edit TextInfo.

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Apr 28, 2014

Comment 1 by Michael Curran <mick@... on 2014-04-28 03:12
In [a068b28]:

Merge branch 't4095' into next. Incubates #4095

Changes:
Added labels: incubating

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Jun 10, 2014

Comment 2 by Michael Curran <mick@... on 2014-06-10 04:33
In [569bf8f]:

Merge branch 't4095'. Fixes #4095

Changes:
Removed labels: incubating
State: closed

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Jun 10, 2014

Comment 3 by mdcurran on 2014-06-10 04:35
Changes:
Milestone changed from next to 2014.3

@nvaccessAuto nvaccessAuto added this to the 2014.3 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant