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

HSEC-2023-0015: better summary #126

Merged
merged 1 commit into from
Nov 7, 2023
+3 −3
Merged

HSEC-2023-0015: better summary #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions advisories/hackage/cabal-install/HSEC-2023-0015.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ type = "FIX"
url = "https://github.com/haskell/cabal/commit/dcfdc9cffd74cade4e8cf3df37c5993413ffd30f"
```

# Summary
# cabal-install uses expired key policies

A problem was recently discovered in `cabal-install`'s
implementation of the Hackage Security protocol that would allow an
Expand All @@ -31,7 +31,7 @@ only a theoretical attack - no keys have been revoked. Release
contacted distributors of older versions (such as Linux
distributions) with a patch that they can apply.

# Background
## Background

Hackage Security is an implementation of [The Update Framework][],
which is a design for a package repository that allows untrusted
Expand Down Expand Up @@ -79,7 +79,7 @@ malicious or obsolete package index.
[key policy file]: https://hackage.haskell.org/root.json
[The Update Framework]: https://theupdateframework.io/

# The Issue
## The Issue

A bug in `cabal-install` caused it to skip the verification of the
key policy file's expiration timestamp. This means that users of
Expand Down