Vulnerability in github.com/edgelesssys/contrast (GHSA-rh99-wc69-c255)

Summary

vulnerability in github.com/edgelesssys/contrast (GHSA-rh99-wc69-c255). Confidential information can be exposed externally. Exploitable via ``CopyFile``. Mitigation: upgrade to `1.19.1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **GHSA-rh99-wc69-c255** has been found in github.com/edgelesssys/contrast. Attackers can target a specific entry point like ``CopyFile`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade github.com/edgelesssys/contrast to **1.19.1** or later. If unsure, ask your IT team or search "github.com/edgelesssys/contrast GHSA-rh99-wc69-c255" on the vendor's site.

GHSA-rh99-wc69-c255 (github.com/edgelesssys/contrast) — CWE-59 / Attack vector: adjacent-network / unauthenticated / no user interaction Attack surface: `CopyFile` Patched: `1.19.1` — apply immediately Workaround: If upgrading is not possible, users can implement the fix in rego and pass it to `contrast generate --policy`. Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

**A vulnerability** (CWE-59) exists in github.com/edgelesssys/contrast. Attackers reach the vulnerable code path via ``CopyFile`` without authentication.

📍 Affected scope

github.com/edgelesssys/contrast — . Attack surface: `CopyFile`.

🔥 Severity

Severity: ?. Confidential information can be exposed externally

🔧 How to fix

Update to **1.19.1**.

🛡️ Workaround

Workaround: If upgrading is not possible, users can implement the fix in rego and pass it to `contrast generate --policy`.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/edgelesssys/contrast' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'github.com/edgelesssys/contrast' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/edgelesssys/contrast` を grep し、稼働しているサービス・バージョンを把握する。
5
Apply temporary workaround mitigate
```
If upgrading is not possible, users can implement the fix in rego and pass it to `contrast generate --policy`.
```
パッチが適用されるまでの応急処置として、If upgrading is not possible, users can implement the fix in rego and pass it to `contrast generate --policy`. を実施。回避策の副作用 (機能低下) を確認した上で。
6
Apply patch patch
```
Upgrade github.com/edgelesssys/contrast to 1.19.1
```
ステージング環境で 1.19.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Go github.com/edgelesssys/contrast

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.19.1"}]}]

References

Metadata

GHSA: GHSA-rh99-wc69-c255
Published: 2026-04-30
First seen on SecPulse: 2 months ago
First-seen source: OSV.dev (Open Source Vulnerabilities)

CWE

CWE-59

Detection sources

OSV.dev (Open Source Vulnerabilities) 2 months ago