### Description

Moby is the open source Linux container runtime and set of components used to build a variety of downstream container runtimes, including Docker CE, Mirantis Container Runtime (formerly Docker EE), and Docker Desktop. Moby allows for building container images using a set of build instructions (usually named and referred to as a "Dockerfile"), and a build context, which is not unlike the CWD in which the Dockerfile instructions are executed.

Containers may be built using a variety of tools and build backends available in the Moby ecosystem; in all cases, builds may not include files outside of the build context (such as using absolute or relative-parent paths). This is enforced through both checks in the build backends, and the containerization of the build process itself.

Versions of Git where CVE-2022-39253 is present and exploited by a malicious repository, when used in combination with Moby, are subject to an unexpected inclusion of arbitrary filesystem paths in the build context, without any visible warning to the user.

This issue was originally reported by Wenxiang Qian of Tencent Blade Team, and the root-cause analysis was performed by Cory Snider of Mirantis, with assistance from Bjorn Neergaard of the same. The issue was then reported to the Git project, and Taylor Blau led the process resolving the root issue in Git.

### Impact

This vulnerability originates in Git, but can be used to violate assumptions that may have security implications for users of Moby and related components. Users may rely on the fact that a build context ensures that outside files cannot be referenced or incorporated using multiple enforcement mechanisms, or expect a warning if this does not hold true. A maliciously crafted Git repository exploiting CVE-2022-39253 can violate this assumption, and potentially include sensitive files that are subsequently uploaded to a container image repository, or disclosed by code inside the resulting container image.

As this issue cannot be triggered remotely, except by users who already have full control over the daemon through the API, and it requires exploiting a vulnerability in Git by convincing a user to build a maliciously crafted repository, the impact in Moby is considered low.

### Patches

Moby 20.10.20, and Mirantis Container Runtime (formerly Docker Enterprise Edition) 20.10.14 will contain mitigations for CVE-2022-39253 when a Git clone is performed by Moby components (on either the daemon or API client side). However, as these mitigations only apply to certain scenarios (build of `git+<protocol>://...` URL contexts) and cannot protect against a malicious repository already on disk, users should update to a version of Git containing patches for CVE-2022-39253 on all their systems running both API clients and daemons.

Specifically, patches in Moby (including patches incorporated from BuildKit) protect against the following:

* `docker build` with the legacy builder (e.g. `DOCKER_BUILDKIT` unset or set to 0) of a Git URL context. Note that depending on available API versions and the CLI version, the Git clone operation can take place on either the client or the daemon side. Both must be updated (or have Git updated) to fully protect this build method.
* `docker build` with the BuildKit builder (e.g. `DOCKER_BUILDKIT=1`) of a Git URL context.
* `docker buildx build` with `BUILDKIT_CONTEXT_KEEP_GIT_DIR=1` of a Git URL context.

Patches in BuildKit incorporated into Docker Compose protect against CVE-2022-39253 during Compose-driven builds of Git URL contexts.

Patches in Moby and related projects such as BuildKit, the Docker CLI, and Docker Compose **cannot** fully protect against CVE-2022-39253, as it may be triggered by a malicious repository already on disk that a unpatched Git client has interacted with (specifically, commands that check out submodules such as `git clone --recursive`, `git submodule update`, etc.  may have already triggered the Git vulnerability).

### Workarounds

While this behavior is unexpected and undesirable, and has resulted in this security advisory, users should keep in mind that building a container entails arbitrary code execution. Users should not build a repository/build context they do not trust, as containerization cannot protect against all possible attacks.

When building with BuildKit (e.g. `docker buildx build` or `docker build` with `DOCKER_BUILDKIT=1`), this issue cannot be exploited unless `--build-arg BUILDKIT_CONTEXT_KEEP_GIT_DIR=1` was also passed, as by default BuildKit will discard the `.git` directory of a Git URL context immediately after cloning and checking out the repository.

### For more information

If you have any questions or comments about this advisory:

* [Open an issue](https://github.com/moby/moby/issues/new)
* Email us at [security@docker.com](mailto:security@docker.com)

Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

Axonflow fixed bugs by implementing multi-tenant isolation and access-control hardening in github.com/getaxonflow/axonflow

mx-chain-go does not treat invalid transaction with wrong username correctly in github.com/multiversx/mx-chain-go

Vitess allows HTML injection in /debug/querylogz and /debug/env in vitess.io/vitess

OpenFGA Authorization Bypass in github.com/openfga/openfga

Path Traversal in gin-vue-admin in github.com/flipped-aurora/gin-vue-admin

File Browser has an Authorization Policy Bypass in Public Share Download Flow in github.com/filebrowser/filebrowser

Chall-Manager's HTTP Gateway is vulnerable to DoS due to missing header timeout in github.com/ctfer-io/chall-manager

Brute-force of token secrets in github.com/superfly/tokenizer

Query smuggling in ch-go library in github.com/ClickHouse/ch-go

Caddy forward_auth copy_headers Does Not Strip Client-Supplied Headers, Allowing Identity Injection and Privilege Escalation in github.com/caddyserver/caddy

Casdoor vulnerable to Stored XSS via Application formCss / formSideHtml in github.com/casdoor/casdoor

Mattermost Cross-Site Request Forgery vulnerability in github.com/mattermost/mattermost-server

Gitea: API Fork Endpoint Authorization Bypass Allows Organization Members to Bypass Repository Creation Restrictions in code.gitea.io/gitea

A malicious JSON patch can cause a panic due to an out-of-bounds write attempt. This can be used as a denial of service vector if exposed to arbitrary user input.

Meshery SQL Injection vulnerability in github.com/layer5io/meshery.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/layer5io/meshery before v0.7.22.

SQL Injection in Cloud Native Computing Foundation Harbor in github.com/goharbor/harbor

Kata Container to Guest micro VM privilege escalation in github.com/kata-containers/kata-containers/src/runtime

terraform-provider-proxmox has insecure sudo recommendation in the documentation in github.com/bpg/terraform-provider-proxmox

File Browser: Colliding username normalization gives two users the same home directory in github.com/filebrowser/filebrowser

Caddy: FastCGI header normalization bypass in forward_auth copy_headers in github.com/caddyserver/caddy

Volcano has insecure permissions in volcano.sh/volcano

Gogs vulnerable to RCE via git rebase --exec argument injection in pull request merge in gogs.io/gogs.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: gogs.io/gogs before v0.14.3.

Cosign verification accepts any valid Rekor entry under certain conditions in github.com/sigstore/cosign

Panic in Path Probe Loss Recovery Handling in github.com/quic-go/quic-go

KubeVirt VMI Denial-of-Service (DoS) Using Pod Impersonation in kubevirt.io/kubevirt

ots has a negative expire override that can bypass its secret retention policy in github.com/Luzifer/ots

Velocidex Velociraptor has an authorization bypass vulnerability in www.velocidex.com/golang/velociraptor.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: www.velocidex.com/golang/velociraptor before v0.76.5.

The html.Parse function in golang.org/x/net/html has an infinite parsing loop when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.

Gogs allows deletion of internal files in github.com/gogs/gogs

Gitea: Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes in code.gitea.io/gitea

Mattermost fails to properly validate User-Agent header tokens in github.com/mattermost/mattermost-server.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/mattermost/mattermost-server/v5 before v5.3.2-0.20260129181235-1346cf529aef.

A malicious proxy/registry can bypass verifyImages rules.

Improper handling of null Unicode character when parsing JSON in github.com/modelcontextprotocol/go-sdk

Rancher does not properly specify ApiGroup when creating Kubernetes RBAC resources in github.com/rancher/rancher.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/rancher/rancher before v2.4.16, from v2.5.0 before v2.5.9.

ICMP Packet Too Large Injection Attack on Linux in github.com/quic-go/quic-go

Rancher users who can create Projects can gain access to arbitrary projects in github.com/rancher/rancher.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/rancher/rancher from v2.8.0 before v2.9.9, from v2.10.0 before v2.10.5, from v2.11.0 before v2.11.1.

Shallow copy bug in geth in github.com/ethereum/go-ethereum

Mattermost Server is vulnerable to XSS through lack of link relationship attributes `noreferrer` and `noopener` in github.com/mattermost/mattermost-server

Nezha vulnerable to cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check in github.com/nezhahq/nezha.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/nezhahq/nezha from v2.0.0 before v2.0.10.

OAuth2 Proxy's Health Check User-Agent Matching Bypasses Authentication in auth_request Mode in github.com/oauth2-proxy/oauth2-proxy

Coder: Devcontainer recreate endpoint missing write authorization allows read-only roles to destroy containers in github.com/coder/coder

Caddy is vulnerable to cross-origin config application via local admin API /load in github.com/caddyserver/caddy/v2

Harbor repository description page has Cross-site Scripting vulnerability in github.com/goharbor/harbor.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/goharbor/harbor before v2.4.0-rc1.0.20250421072404-a13a16383a41.

Free5GC PCF: Missing authentication middleware in Npcf_SMPolicyControl allows access to SM policy handlers and disclosure of subscriber SUPI in github.com/free5gc/pcf

free5gc UDR improper path validation allows unauthenticated deletion of Traffic Influence Subscriptions in github.com/free5gc/udr

The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public key authentication. RSA moduli are now limited to 8192 bits, and DSA parameters are validated per FIPS 186-2.

Incus has an argument injection in backup compression algorithm leading to AFW and ACE in github.com/lxc/incus

Navidrome allows an authentication bypass in Subsonic API with non-existent username in github.com/navidrome/navidrome

Nezha Dashboard: DDNS and Notification credential exposure via unredacted list API in github.com/nezhahq/nezha.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/nezhahq/nezha before v2.2.5.

# Summary

In the threshold signature scheme, participants start by dividing secrets into shares using a secret sharing scheme. The Verifiable Secret Sharing scheme generates shares from the user’s IDs but does not properly validate them. Using a malicious ID will make other users reveal their secrets during the secret-sharing procedure. In addition, a second issue resulting from lack of validation could cause nodes to crash when sent maliciously formed user IDs.

# Details

The creation of Parties IDs does not properly validate for maliciously chosen IDs. Parties generate the secret shares in `binance-chain/tss-lib` codebase that `keep-network/keep-ecdsa` uses by evaluating the polynomial with the other parties’ IDs. It is critical that these party ids are non-zero because evaluating the polynomial at point 0 reveals the secret.

There is a check that these ids are not zero, but this is insufficient since it is not performed modulo the curve order. Therefore, one can set their ID equal to the order of the elliptic curve, which equals 0 during the polynomial evaluation modulo the curve order.
```
    shares := make(Shares, num)
    for i := 0; i < num; i++ {
        if indexes[i].Cmp(big.NewInt(0)) == 0 {
            return nil, nil, fmt.Errorf("party index should not be 0")
        }
        share := evaluatePolynomial(ec, threshold, poly, indexes[i])
        shares[i] = &Share{Threshold: threshold, ID: indexes[i], Share: share}
    }
```
(https://github.com/binance-chain/tss-lib/blob/73560daec7f83d7355107ea9b5e59d16de8765be/crypto/vss/feldman_vss.go#L64-L70)

Thus, a party with an ID equal to the order of the curve will receive the secret key as its share.

Another issue with the tss-lib implementation was the lack of verification for modularly equal user IDs that can cause nodes to crash during key generation or resharing.

# Timeline

### 6 December 2021, 20:28 CET
The team is informed by Trail of Bits about the issue in `binance-chain/tss-lib`. The vulnerability was already disclosed with Binance and they have implemented fixes in their recent commits. We are advised to update our dependency to the most recent `binance-chain/tss-lib` version.

### 7 December 2021, 9:10 CET
The team confirms with Trail of Bits we started the work on a fix.

### 7 December 2021, 20:03 CET
The team informs Trail of Bits that we found a potential problem in Binance's fix that may lead to the signing code failing with Go panic. We identified the problematic line and suggested its removal.

To address the vulnerability in the protocol, it is required to ensure that:
- all indexes are non-zero,
- all indexes are non-zero modulo the curve order,
- all indexes are unique modulo the curve order.

The first two are guarded in `CheckIndexes` function by:
```
vMod := new(big.Int).Mod(v, ec.Params().N)
if vMod.Cmp(zero) == 0 {
  return nil, errors.New("party index should not be 0")
}
```
The last one is guarded by:
```
if sortutil.Dedupe(sortutil.BigIntSlice(dup)) < len(indexes) {
  return nil, errors.New("duplicate in indexes")
}
```
However, `CheckIndexes` was additionally modified to update values of passed indexes by doing `indexes[i] = vMod`.

This line was not backward-compatible and caused signatures to fail with `panic: runtime error: invalid memory address or nil pointer dereference` in case the signing group was generated with at least one `PartyID.Key` higher than `ec.Params().N`. This would also be problematic for new code that constructs such `PartyID` - we tested that key generation completed successfully but signing failed with the mentioned panic.

### 8 December 2021, 12:49 CET
Trail of Bits confirmed the line we flagged is not critical to the security of the protocol.

### 8 December 2021, 15:29 CET
The team informed Trail of Bits we are planning to open a PR to `binance-chain/tss-lib` with a fix and we suggest extending the embargo for communicating this issue for one more week, until Friday, Dec 17h to give everyone more time update their code given the problem was found. We also ask Trail of Bits to get in touch with Binance to review our fix given that we are not going to provide a sufficient explanation in the commit and PR description to do not threaten the security of projects that have already upgraded their dependency.

### 8 December 2021, 18:17 CET

The team informs Trail of Bits about opening a PR https://github.com/binance-chain/tss-lib/pull/155 and explains all the details of the issue.

The problematic scenario is:

1. We start the keygen by creating `PartyID` for each member. The `PartyID` struct has `Id` and `Key` fields. We set `PartyID.Key` that is higher than the elliptic curve's `N`.
2. This goes to tss-lib which starts the round 1 code (`ecdsa/keygen/round_1.go`). It takes `PartyID.Key` of each member and assembles the `ids` slice. This slice is thrown into `CheckIndexes` which overwrites each element by doing the modulo `N`.
3. After returning from `CheckIndexes` the modified `ids` slice is used to set the `Ks` slice in the final `LocalPartySaveData` which is received by each group member as keygen final result.
4. Each member takes this `LocalPartySaveData` and saves it on disk.
5. Upon signing, we do the same as in point 1, so we construct `PartyID`s in the same way and start the protocol. At this point, `PartyID.Key` is higher than curve's `N`.
6. Before starting round 1 of signing, `LocalPartySaveData` obtained at keygen and our `PartyID`s built at point 5 are used in `BuildLocalSaveDataSubset` to build a new `LocalPartySaveData` instance.
7. `BuildLocalSaveDataSubset` is the place where things go wrong because `Key` field of each `PartyID` from point 5 doesn't correspond to encoded `Ks` elements of `LocalPartySaveData` obtained after keygen, the final `LocalPartySaveData` is corrupted, and cause panic upon validation before signing round 1.

### 8 December 2021, 21:50 CET

Trail of Bits confirms they are going to followup with Binance and they agree to extend the embargo by a week.

### 8 December 2021, 15:16 CET

Trail of Bits validates the problematic scenario we described and our fix. Trail of Bits reaches to Binance and recommends merging our fix and in addition to some other fixes that would secure the code to do not panic even if `LocalPartySaveData` has corrupted data.

### 10 December 2021, 8:16 CET

Binance merges our fix https://github.com/binance-chain/tss-lib/commit/cd95cee01ea2af6d4aa8316612803be944d5369a

### 13 December 2021, 8:35 CET

Binance applies more fixes so that even in case of `LocalPartySaveData` corrupted, the code is not going to panic.

### 15 December 2021

The team releases a new version of the client, v1.8.1, and announces the need for an upgrade.
https://github.com/keep-network/keep-ecdsa/releases/tag/v1.8.1

Gogs vulnerable to Cross-site Scripting in gogs.io/gogs

Exposure of Sensitive Information in Pomerium in github.com/pomerium/pomerium

Komari vulnerable to 2FA Authentication Bypass in github.com/komari-monitor/komari

OpenBao's System Backend allows Unauthorized Management of the containing Namespace in github.com/openbao/openbao

This vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.

The vulnerability is determined to be low severity.

### Impact

This vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.  

### Patches

The issue have been patched in all repositories. The following versions should be updated to as soon as possible:

[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  
D 3.0.1  
[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  
Elixir 3.0.0  
[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  
[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  
[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  
Kotlin 1.1.0  
Lua 3.0.1  
[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  
Perl 3.0.0  
[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  
[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  
[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  
Scala 3.0.1  
Swift 1.0.1  

If you are using any of the earlier packages, please update to latest.

### Workarounds

The issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be
000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not
000x.

### For more information

If you have any questions or comments about this advisory:
* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)
* Email us at [Personnummer Email](mailto:security@personnummer.dev)

Finality Provider vulnerable to anti-slashing bypassing due to misconfiguration in github.com/babylonlabs-io/finality-provider

Fleet vulnerable to SQL Injection in MDM bootstrap package by authenticated team or global admin in github.com/fleetdm/fleet

In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters in github.com/cilium/cilium

Smokescreen SSRF via deny list bypass in github.com/stripe/smokescreen

Due to the misuse of log.Fatalf, Coraza may crash after receiving crafted requests from attackers.

Inspektor Gadget uses unsanitized ANSI Escape Sequences In `columns` Output Mode in github.com/inspektor-gadget/inspektor-gadget

Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation in github.com/argoproj/argo-cd

Clients can cause a panic in SSH servers. An attacker can craft an authentication request message for the “gssapi-with-mic” method which will cause NewServerConn to panic via a nil pointer dereference if ServerConfig.GSSAPIWithMICConfig is nil.

Users can create a keyspace containing '/'. Future attempts to view keyspaces from some tools (including VTAdmin and "vtctldclient GetKeyspaces") receive an error.

BoxLite: Permission Bypass Allows Modification of Read-Only Files in github.com/boxlite-ai/boxlite/sdks/go

(This advisory is canonically https://advisories.nats.io/CVE/CVE-2020-26892.txt )

## Problem Description

NATS nats-server through 2020-10-07 has Incorrect Access Control because of how expired credentials are handled.

The NATS accounts system has expiration timestamps on credentials; the <https://github.com/nats-io/jwt> library had an API which encouraged misuse and an `IsRevoked()` method which misused its own API.

A new `IsClaimRevoked()` method has correct handling and the nats-server has been updated to use this.  The old `IsRevoked()` method now always returns true and other client code will have to be updated to avoid calling it.

The CVE identifier should cover any application using the old JWT API, where the nats-server is one of those applications.


## Affected versions

#### JWT library

 * all versions prior to 1.1.0
 * fixed after nats-io/jwt PR 103 landed (2020-10-06)

#### NATS Server

 * Version 2 prior to 2.1.9
   + 2.0.0 through and including 2.1.8 are vulnerable.
 * fixed with nats-io/nats-server PRs 1632, 1635, 1645


## Impact

Time-based credential expiry did not work.


## Workaround

Have credentials which only expire after fixes can be deployed.


## Solution

Upgrade the JWT dependency in any application using it.

Upgrade the NATS server if using NATS Accounts.

NATS Server and Streaming Server fails to enforce negative user permissions, may allow denied subjects in github.com/nats-io/nats-server

Non-interactive Tailscale SSH sessions on FreeBSD may use the effective group ID of the tailscaled process in tailscale.com

SiYuan importStdMd: unvalidated localPath imports arbitrary host directories as persistent notes in github.com/siyuan-note/siyuan

CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation in github.com/cilium/cilium

DragonFly vulnerable to panics due to nil pointer dereference when using variables created alongside an error in d7y.io/dragonfly

Gogs vulnerable to Stored XSS via Mermaid diagrams in gogs.io/gogs.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: gogs.io/gogs before v0.13.4.

Arcane Vulnerable to Unauthenticated Disclosure of Custom Compose Template Content (incl. `.env` secrets) in github.com/getarcaneapp/arcane/backend

Traefik has an StripPrefixRegex Middleware Authorization Bypass via Path/RawPath Desync in github.com/traefik/traefik

The Verify function in crypto/dsa passed certain parameters unchecked to the underlying big integer library, possibly leading to extremely long-running computations, which in turn makes Go programs vulnerable to remote denial of service attacks. Programs using HTTPS client certificates or the Go SSH server libraries are both exposed to this vulnerability.

Parsing PKIX distinguished names containing the string "=#" can cause excessive memory consumption.

Mattermost Server SAML implementation does not require encryption or signature verification as default in github.com/mattermost/mattermost-server.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/mattermost/mattermost-server before v3.8.1-0.20170504181128-4f074fed0d65.

BuildKit provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special security.insecure entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.

1Panel – CAPTCHA Bypass via Client-Controlled Flag in github.com/1Panel-dev/1Panel

A maliciously crafted path can cause Get and other query functions to consume excessive amounts of CPU and time.

Mattermost allows other users to determine when users had read channels via channel member objects in github.com/mattermost/mattermost-server.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/mattermost/mattermost/server/v8 before v8.0.0-20250905150616-ba86dfc5876b6.

Gogs vulnerable to a bypass of CVE-2024-55947 in gogs.io/gogs

OpenKruise PodProbeMarker is Vulnerable to SSRF via Unrestricted Host Field in github.com/openkruise/kruise

Casdoor CORS misconfiguration (GHSL-2024-035) in github.com/casdoor/casdoor

Brokercap Bifrost subject to authentication bypass when using HTTP basic authentication in github.com/brokercap/Bifrost

Ollama Vulnerable to Denial of Service (DoS) via Crafted GZIP in github.com/ollama/ollama

Babylon's BIP322 signature implementation is not fully compliant to the spec in github.com/babylonlabs-io/babylon

Mattermost Server has intermittent Authorization bypass for resource-owners in github.com/mattermost/mattermost-server

Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server in github.com/argoproj/argo-cd

File Browser: Symlink following lets scoped users read, overwrite, and share files outside their filebrowser scope in github.com/filebrowser/filebrowser

User login denial of service in github.com/google/fscrypt

Hashicorp Vault Community vulnerable to Generation of Error Message Containing Sensitive Information in github.com/hashicorp/vault

HashiCorp Vault Vulnerable to Denial-of-Service via Unauthenticated Root Token Generation/Rekey Operations in github.com/hashicorp/vault

LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic in github.com/authzed/spicedb.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: .

CVE-2024-47218 in github.com/vesoft-inc/nebula

### Impact

The vulnerability allows a third party to derive a valid proof from a valid initial tuple {proof, public_inputs}, corresponding to the same public inputs as the initial proof. It is due to a randomness being generated using a small part of the scratch memory describing the state, allowing for degrees of freedom in the transcript.

Note that the impact is limited to the PlonK verifier smart contract.

### Patches

We still use a hash function on some data to have a pseudo rng, but instead of hashing the first 32 bytes of the state (
` let random := mod(keccak256(state, 0x20), r_mod)` )

we hash the whole state at this point of the verifier as if it was a Fiat Shamir transcript:
```
        mstore(mPtr, mload(add(state, STATE_FOLDED_DIGESTS_X)))
        mstore(add(mPtr, 0x20), mload(add(state, STATE_FOLDED_DIGESTS_Y)))
        mstore(add(mPtr, 0x40), calldataload(add(aproof, PROOF_BATCH_OPENING_AT_ZETA_X)))
        mstore(add(mPtr, 0x60), calldataload(add(aproof, PROOF_BATCH_OPENING_AT_ZETA_Y)))
        mstore(add(mPtr, 0x80), calldataload(add(aproof, PROOF_GRAND_PRODUCT_COMMITMENT_X)))
        mstore(add(mPtr, 0xa0), calldataload(add(aproof, PROOF_GRAND_PRODUCT_COMMITMENT_Y)))
        mstore(add(mPtr, 0xc0), calldataload(add(aproof, PROOF_OPENING_AT_ZETA_OMEGA_X)))
        mstore(add(mPtr, 0xe0), calldataload(add(aproof, PROOF_OPENING_AT_ZETA_OMEGA_Y)))
        mstore(add(mPtr, 0x100), mload(add(state, STATE_ZETA)))
        mstore(add(mPtr, 0x120), mload(add(state, STATE_GAMMA_KZG)))
        let random := staticcall(gas(), 0x2, mPtr, 0x140, mPtr, 0x20)
```

### Workarounds

In the function `batch_verify_multi_points`, the variable `random` (corresponding to `u` in the paper, step 12 of the [plonk](https://eprint.iacr.org/2019/953.pdf) verification process) should depend on `state_folded_digests_x`, `state_folded_digests_y`, `proof_grand_product_commitment_x`, `proof_grand_product_commitment_y` and `state_zeta` (by hashing those values for instance).


Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content.

The "#cgo pkg-config:" directive in a Go source file provides command-line arguments to provide to the Go pkg-config command. An attacker can provide a "--log-file" argument to this directive, causing pkg-config to write to an attacker-controlled location.

CVE-2024-21527 in github.com/gotenberg/gotenberg

CVE ID↕	Published↕	CVSS↑
GHSA-vp35-85q5-9f25	Nov 11, 2022	N/A
GO-2022-1038	Oct 6, 2022	N/A
GO-2026-5290	Jun 25, 2026	N/A
GO-2023-1806	Aug 20, 2024	N/A
GO-2024-3306	Dec 12, 2024	N/A
GO-2022-1081	Aug 21, 2024	N/A
GO-2023-1560	Aug 20, 2024	N/A
GO-2026-4738	Apr 7, 2026	N/A
GO-2025-3809	Jul 28, 2025	N/A
GO-2023-1914	Jul 25, 2023	N/A
GO-2025-3603	Apr 22, 2025	N/A
GO-2026-4639	Mar 10, 2026	N/A
GO-2026-5697	Jun 25, 2026	N/A
GO-2024-3097	Aug 30, 2024	N/A
GO-2026-6074	Jul 27, 2026	N/A
GO-2021-0076	Apr 14, 2021	N/A
GO-2024-3050	Aug 6, 2024	N/A
GO-2022-0853	Aug 21, 2024	N/A
GO-2026-4517	Feb 23, 2026	N/A
GO-2026-4395	Feb 5, 2026	N/A
GO-2026-6024	Jul 22, 2026	N/A
GO-2026-5346	Jul 24, 2026	N/A
GO-2024-3034	Aug 6, 2024	N/A
GO-2026-5580	Jun 25, 2026	N/A
GO-2026-4309	Jan 13, 2026	N/A
GO-2025-3735	Jun 3, 2025	N/A
GO-2025-4105	Nov 17, 2025	N/A
GO-2026-5413	Jun 25, 2026	N/A
GO-2026-5078	Jun 25, 2026	N/A
GO-2026-4441	Feb 5, 2026	N/A
GO-2024-2970	Jul 9, 2024	N/A
GO-2026-5721	Jun 25, 2026	N/A
GO-2026-4725	Mar 26, 2026	N/A
GO-2022-1180	Dec 27, 2022	N/A
GO-2026-4770	Mar 23, 2026	N/A
GO-2024-2768	Jun 10, 2024	N/A
GO-2024-3302	Dec 4, 2024	N/A
GO-2025-3647	May 5, 2025	N/A
GO-2022-0771	Aug 21, 2024	N/A
GO-2025-4058	Oct 30, 2025	N/A
GO-2026-5821	Jul 7, 2026	N/A
GO-2026-5147	Jun 25, 2026	N/A
GO-2026-5922	Jul 7, 2026	N/A
GO-2026-4537	Feb 26, 2026	N/A
GO-2025-3825	Jul 29, 2025	N/A
GO-2026-5189	Jun 25, 2026	N/A
GO-2026-5396	Jun 25, 2026	N/A
GO-2026-5018	May 22, 2026	N/A
GO-2026-5808	Jul 7, 2026	N/A
GO-2025-3484	Mar 3, 2025	N/A
GO-2026-5832	Jul 7, 2026	N/A
GHSA-gp6j-vx54-5pmf	Jan 6, 2022	N/A
GO-2022-1060	Aug 21, 2024	N/A
GO-2022-0413	Aug 21, 2024	N/A
GO-2025-3873	Aug 18, 2025	N/A
GO-2026-5517	Jun 25, 2026	N/A
GHSA-hv53-vf5m-8q94	Feb 11, 2022	N/A
GO-2025-4236	Dec 15, 2025	N/A
GO-2026-4913	Apr 2, 2026	N/A
GO-2025-3635	Apr 22, 2025	N/A
GO-2022-0429	Aug 21, 2024	N/A
GO-2023-1874	Jul 5, 2023	N/A
GO-2026-5068	Jun 25, 2026	N/A
GO-2026-5418	Jun 25, 2026	N/A
GO-2021-0227	Feb 17, 2022	N/A
GO-2023-1717	Apr 12, 2023	N/A
GO-2026-5392	Jun 25, 2026	N/A
GHSA-2c64-vj8g-vwrq	May 21, 2021	N/A
GO-2024-2980	Jul 12, 2024	N/A
GO-2023-1671	Aug 20, 2024	N/A
GO-2026-4708	Mar 26, 2026	N/A
GO-2026-5914	Jul 7, 2026	N/A
GO-2025-3970	Sep 24, 2025	N/A
GO-2026-4454	Feb 17, 2026	N/A
GO-2026-5340	Jun 25, 2026	N/A
GO-2026-5180	Jun 25, 2026	N/A
GO-2022-0166	May 24, 2022	N/A
GO-2023-1589	Jul 11, 2023	N/A
GO-2026-4478	Feb 17, 2026	N/A
GO-2024-2497	Feb 7, 2024	N/A
GO-2025-4209	Dec 15, 2025	N/A
GO-2021-0265	Aug 15, 2022	N/A
GO-2025-4133	Nov 25, 2025	N/A
GO-2025-4225	Dec 15, 2025	N/A
GO-2026-4549	Feb 27, 2026	N/A
GO-2024-3087	Aug 30, 2024	N/A
GO-2022-1023	Aug 21, 2024	N/A
GO-2025-3548	Mar 31, 2025	N/A
GO-2025-4159	Nov 25, 2025	N/A
GO-2026-4297	Jan 13, 2026	N/A
GO-2022-0499	Aug 21, 2024	N/A
GO-2026-5055	Jun 16, 2026	N/A
GO-2022-0340	Aug 21, 2024	N/A
GO-2025-3663	May 6, 2025	N/A
GO-2026-5247	Jun 25, 2026	N/A
GO-2026-4465	Feb 17, 2026	N/A
GO-2024-3155	Sep 26, 2024	N/A
GHSA-7p92-x423-vwj6	Oct 17, 2023	N/A
GO-2026-4339	Jan 28, 2026	N/A
GO-2024-2996	Jul 22, 2024	N/A

Know every vulnerability
before it knows you.

go CVE Vulnerabilities — DevGuard Vulnerability Database

Know every vulnerabilitybefore it knows you.

go CVE Vulnerabilities — DevGuard Vulnerability Database

Know every vulnerability
before it knows you.