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

[release-23.05] forgejo: mark as insecure #271199

Merged
merged 1 commit into from
Dec 1, 2023
Merged
Changes from all commits
Commits
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
23 changes: 23 additions & 0 deletions pkgs/applications/version-management/forgejo/default.nix
Original file line number Diff line number Diff line change
Expand Up @@ -118,5 +118,28 @@ buildGoModule rec {
maintainers = with lib.maintainers; [ emilylange urandom bendlas ];
broken = stdenv.isDarwin;
mainProgram = "gitea";
knownVulnerabilities = [
''
Forgejo's API and web endpoints before version 1.20.5-1 are affected by multiple
critical security vulnerabilities.

Non-exhaustive list:
- reveal comments from issues and pull-requests from private repositories
- delete comments from issues and pull-requests
- get private release attachments
- delete releases and tags
- get ssh deployment keys (public key)
- get OAuth2 applications (except for the secret)
- 2FA not being enforced for the container registry login (docker login)

There isn't a clear way how to backport and validate all those fixes to the now EOL
forgejo 1.19.x and we, the forgejo nixpkgs maintainers, decided against bumping the
release from 1.19.x to 1.20.x due to its breaking nature.
Given nixpkgs 23.11 has been released by now and nixpkgs 23.05 will reach EOL very
soon (2023-12-31), please update to nixpkgs 23.11 instead.

Upstream: https://forgejo.org/2023-11-release-v1-20-5-1/
''
];
};
}