Vulnerability in Registrator (CVE-2025-52483)

Summary

Vulnerability in Registrator (CVE-2025-52483). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.9.5 or later.

Original description

The description as published by the source.

Impact

If the clone URL returned by GitHub is malicious (or can be injected using upstream vulnerabilities), a shell script injection can occur within the withpasswd() function. This can then lead to a potential RCE.

Patches

Users should upgrade immediately to v1.9.5. All prior versions are vulnerable.

Workarounds

None

References

Fixed by: https://github.com/JuliaRegistries/Registrator.jl/pull/448 (which is available in v1.9.5).

Credits

Thanks to splitline from the DEVCORE Research Team for reporting this issue.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-52483 has been found in Registrator.
Successful exploitation can lead to full system takeover.
What to do: upgrade Registrator to 1.9.5 or later.
If unsure, ask your IT team or search "Registrator CVE-2025-52483" on the vendor's site.

CVE-2025-52483 (Registrator)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.9.5 — apply immediately
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 (unclassified) exists in Registrator.

📍 Affected scope

Check the vendor advisory for the affected versions of Registrator.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.9.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

Response actions

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

1
Identify exposure identify
```
grep -r 'Registrator' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Registrator を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Registrator to 1.9.5
```
ステージング環境で 1.9.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Julia Registrator

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

References

web github.com
web github.com