Vulnerability in github.com/datacharmer/dbdeployer (CVE-2020-26277)
Summary
Vulnerability in github.com/datacharmer/dbdeployer (CVE-2020-26277). Data can be tampered with by attackers. Exploitable via fake_file. Mitigation: upgrade to 1.58.2 or later.
Original description
The description as published by the source.
Impact
Users unpacking a tarball through dbdeployer may use a maliciously packaged tarball that contains symlinks to files external to the target. In such scenario, an attacker could induce dbdeployer to write into a system file, thus altering the computer defences.
Mitigating factors
For the attach to succeed, the following factors need to contribute:
- The user is logged in as root. While dbdeployer is usable as root, it was designed to run as unprivileged user.
- The user has taken a tarball from a non secure source, without testing the checksum. When the tarball is retrieved through dbdeployer, the checksum is compared before attempting to unpack.
Analysis
An attacker could inject a symbolic link into the tarball, so that a file could result into fake_file -> /etc/passwd or some equally important file.
As it is now, dbdeployer would create the symlink as defined, with a local file fake_file linked to /etc/passwd. The danger here is that any process with the privileges to write to both fake_file and /etc/passwd could overwrite the system file. Even without malicious intent, this could result in the system to become unusable.
As noted above, the user must have write privileges to the target file to do the damage.
Remedies
It has been suggested that the extract procedure use filepath.EvalSymlinks to determine whether the target is within the extraction directory. Unfortunately, this approach is unavailable in this context, because it wou…
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-2020-26277 has been found in github.com/datacharmer/dbdeployer.
Attackers can target a specific entry point like fake_file over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade github.com/datacharmer/dbdeployer to 1.58.2 or later.
If unsure, ask your IT team or search "github.com/datacharmer/dbdeployer CVE-2020-26277" on the vendor's site.
CVE-2020-26277 (github.com/datacharmer/dbdeployer) — CWE-59
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: fake_file / filepath.EvalSymlinks
Patched: 1.58.2 — 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.
A vulnerability (CWE-59) exists in github.com/datacharmer/dbdeployer. Attackers reach the vulnerable code path via fake_file without authentication.
Check the vendor advisory for the affected versions of github.com/datacharmer/dbdeployer. Attack surface: fake_file / filepath.EvalSymlinks.
Severity: ?. Data can be tampered with by attackers.
Update to 1.58.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/datacharmer/dbdeployer' . 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
-
1Identify exposure identify
grep -r 'github.com/datacharmer/dbdeployer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/datacharmer/dbdeployerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/datacharmer/dbdeployer to 1.58.2ステージング環境で 1.58.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com