https://github.com/justingrote/secretmanagement.chromium

A Powershell SecretManagement vault extension for accessing the passwords stored in Chromium-based browsers.
https://github.com/justingrote/secretmanagement.chromium

powershell secretmanagement secretmanagement-extension

Last synced: about 2 months ago
JSON representation

A Powershell SecretManagement vault extension for accessing the passwords stored in Chromium-based browsers.

• Host: GitHub
• URL: https://github.com/justingrote/secretmanagement.chromium
• Owner: JustinGrote
• License: mit
• Created: 2021-01-15T00:58:33.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2021-03-11T06:57:27.000Z (almost 4 years ago)
• Last Synced: 2023-03-08T10:14:13.188Z (almost 2 years ago)
• Topics: powershell, secretmanagement, secretmanagement-extension
• Language: PowerShell
• Homepage:
• Size: 2.29 MB
• Stars: 29
• Watchers: 3
• Forks: 6
• Open Issues: 0
• Metadata Files:
  • Readme: README.MD
  • License: LICENSE

Awesome Lists containing this project

README

        
![Banner](images/banner.png)

[![PowerShell Gallery](https://img.shields.io/powershellgallery/dt/SecretManagement.Chromium?label=Powershell%20Gallery&logo=powershell)](https://www.powershellgallery.com/packages/SecretManagement.Chromium)

## Overview

This is a Vault Extension for the [Microsoft.PowerShell.SecretManagement](https://github.com/powershell/secretmanagement) module. It allows you to quickly detect and access passwords saved in Chromium-based browsers such as Google Chrome and Microsoft Edge. You can use credentials saved in the browser to access other resources via PowerShell.

![Demo](images/demo.gif)

## Requirements

- **PowerShell 7** (Windows PowerShell 5.1 support on the roadmap)

- **Microsoft Windows** (Linux/OSX support on the roadmap)

## Quickstart

```powershell

Install-Module SecretManagement.Chromium

#Autodetect Chrome and Edge

Register-ChromiumSecretVault -Verbose

#View the vaults

Get-SecretVault

#Get a list of all secrets in the vaults

Get-SecretInfo

```

## Features

1. Automatic discovery of Chrome and Edge (all versions)

![demodiscovery](images/demo-discovery.gif)

1. Fetching secrets, including secrets synced from Android

1. Powerful filter and search syntax

## Get-SecretInfo Filter Usage

Secrets are presented in username|domain format, because usernames can contain @,\, and whitespace symbols, hence the somewhat unusual naming format.

If there is a conflict and two secrets have the same username and URL combination, the database ID of that entry may be appended to the entry with a colon

You can still use this entry to get this specific entry

You can search for secrets in the following ways:

1. User + Domain Explicit Search (`myuser|https://www.twitter.com/`)

1. Explicit URL (`https://www.twitter.com/`). All components, including trailing backspaces, are required!

1. Wildcard URL Search (`*twitter*`)

1. Explicit User Search (`myuser|`)

1. Wildcard User Search (`my*|`) - Note the trailing `|` to indicate you want to search user and not URL 

1. User + Domain Wildcard Search (`*m*|*tw*`)

## FAQ

1. **Why are the secret names so "ugly"?**

   

   Because of a [limitation in the SecretManagement API](https://github.com/PowerShell/SecretManagement/issues/46). If this annoys you, upvote this issue!

1. **This was too easy, I didn't know Chromium was so insecure!**

    It's not insecure per se, your passwords are encrypted at rest by Windows DPAPI and the key is "bound" to your user profile and windows login, so you have to be logged into your profile in order for this to work. Go ahead, try copying the files to another machine or a different user profile on the same machine and try it, it will fail. This is more of a Single Sign-On approach.

    That said, this is also a lesson that any program you run in your userspace can potentially harvest these passwords since it runs in the context of your username, so don't click that email link!