New issue
Advanced search Search tips

Issue 806512 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Password Visible After Removal

Reported by anuraggu...@gmail.com, Jan 27 2018

Issue description

Chrome Version       : Version 63.0.3239.132 (Official Build) (64-bit)
URLs (if applicable) : chrome://settings/passwords
Other browsers tested: Chrome Browser Problem

What steps will reproduce the problem?
(1) First you click on view password for anyone of the Saved passwords
(2) Then you click on view password.
(3) Then you remove password for the same and you will still be able see the

What is the expected result?
If I remove any one the visible Saved Password, it should be visible if I remove the password.

What happens instead?
If I go to Manage Passwords in Settings and view anyone of the saved passwords, and then click on remove password, the password is still visible with the next in line Saved passwords


Attached screenshot of the same. Earlier there were 3 Saved Passwords. I click on view password of the first one in the list. Then I click on remove password from 3 dotted icon. Now the still you can the password on top of the list. This is a major securing and functionality issue.

 
Remove Password.PNG
36.8 KB View Download
Do you still see the issue after updating to Chrome 64?
No, I don't. The issue is resolved now. Does this mean I won't be rewarded?
Labels: Needs-Triage-M63
What does it mean?
I don't think they changed anything based on your report, otherwise there would have been an automated comment informing you that "The following revision refers to this bug". Even if they did fix the issue based on your report, I don't think they would give you a reward, because https://chromium.googlesource.com/chromium/src/+/master/docs/security/faq.md#Why-arent-physically_local-attacks-in-Chromes-threat-model.
Labels: Triaged-ET
Status: WontFix (was: Unconfirmed)
anuraggupta.hits@ Thanks for the feedback.

As per comment #2, closing this issue as reporter has confirmed that the issue is not seen on the latest Chrome builds.

Please feel free to raise a new bug if the issue is reproducible on the latest Chrome builds.

Thanks..

Sign in to add a comment