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.

Sign up for GitHub

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

Jump to bottom

Added CVE-2020-16253 for pghero #451

Merged
merged 2 commits into from
Aug 10, 2020
Merged

Added CVE-2020-16253 for pghero #451

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f021434
Added CVE-2020-16253 for pghero
ankane Aug 4, 2020
9e602b6
Update CVE-2020-16253.yml
reedloden Aug 10, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions gems/pghero/CVE-2020-16253.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
gem: pghero
cve: 2020-16253
ghsa: v6fx-752r-ccp2
url: https://github.com/ankane/pghero/issues/330
title: CSRF Vulnerability with Non-Session Based Authentication
date: 2020-08-04
description: |
The PgHero dashboard is vulnerable to CSRF with non-session based authentication methods.

## Impact
The PgHero dashboard is vulnerable to cross-site request forgery (CSRF). This affects the Docker
image, Linux packages, and in specific cases, the Ruby gem. The Ruby gem is vulnerable with
non-session based authentication methods like basic authentication - session-based authentication
methods (like Devise's default authentication) are not affected.

A CSRF attack works by getting an authorized user to visit a malicious website and then performing
requests on behalf of the user. In this instance, actions include:

1. Canceling running queries
2. Running `EXPLAIN` on queries (without seeing the results, but can be used for denial of service
and other attacks)
3. Resetting query stats (running `pg_stat_statements_reset()`)

patched_versions:
- ">= 2.7.0"