Security readout for executives and security teams
Plain-English summary
Biscom Secure File Transfer versions 5.0.0000 through 5.1.1026 allowed an authenticated user to place AngularJS expressions in their Display Name. Those expressions could run when another authenticated user viewed that name. The vendor-fixed version is 5.1.1028.
Executive priority
Treat this as a moderate-priority legacy application issue. Prioritize upgrade if Biscom Secure File Transfer is internet-facing, widely accessible internally, or used by high-trust users handling sensitive file transfers.
Technical view
This is an authenticated stored AngularJS expression injection in the Display Name field. The CVE states a valid AngularJS expression wrapped in double curly braces is evaluated by other authenticated viewers. No CVSS, CWE, or detailed impact scope is provided in the bundle.
Likely exposure
Exposure is limited to Biscom Secure File Transfer deployments running versions 5.0.0000 through 5.1.1026. The attacker must already be authenticated, and impact depends on how the application renders and privileges affected user sessions.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. A public social-media reference exists, but the supplied evidence does not establish exploitation in the wild.
Researcher notes
Evidence is sparse: the CVE names the vulnerable field, affected range, authenticated precondition, evaluation behavior, and fixed version. It does not provide CVSS, CWE, exploit status, or complete impact details, so validation should focus on version and rendering behavior.
Mitigation direction
- Upgrade Biscom Secure File Transfer to 5.1.1028 or later.
- Review Biscom advisory for supported upgrade guidance.
- Restrict authenticated access until affected instances are upgraded.
- Review user profile Display Name values for suspicious AngularJS-style content.
Validation and detection
- Inventory Biscom Secure File Transfer instances and record exact versions.
- Confirm no production instance runs 5.0.0000 through 5.1.1026.
- Check whether Display Name content is rendered to other authenticated users.
- Review application logs for unusual profile Display Name changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-5246 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://twitter.com/i_bo0om/status/885050741567750145CVE reference · x_refsource_MISC
- https://cve.biscom.com/bis-sft-cv-0004/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.