Vulnerability in Biscom Secure File Transfer (CVE-2017-5246)
Summary
Vulnerability in Biscom Secure File Transfer (CVE-2017-5246). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.1.1028 or later.
Original description
The description as published by the source.
Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field. An authenticated user can populate this field with a valid AngularJS expression, wrapped in double curly-braces ({{ }}). This expression will be evaluated by any other authenticated user who views the attacker's display name. Affected versions are 5.0.0000 through 5.1.1026. The Issue is fixed in 5.1.1028.
Source: NIST National Vulnerability Database NVD
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-2017-5246 has been found in Biscom Secure File Transfer.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade Biscom Secure File Transfer to 5.1.1028 or later.
If unsure, ask your IT team or search "Biscom Secure File Transfer CVE-2017-5246" on the vendor's site.
CVE-2017-5246 (Biscom Secure File Transfer) — CWE-74 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.1.1028 — 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-74) exists in Biscom Secure File Transfer.
Check the vendor advisory for the affected versions of Biscom Secure File Transfer.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 5.1.1028.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Biscom Secure File Transfer を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Biscom Secure File Transfer to 5.1.1028ステージング環境で 5.1.1028 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory twitter.com
- web cve.biscom.com