dbcve.org
Tg\/s3.2 FirmwareOperating system · Abb

CVE-2019-19106

CRITICAL · 9.1 CVSS v3.1 Published 2020-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper implementation of Access Control in ABB Telephone Gateway TG/S 3.2 and Busch-Jaeger 6186/11 Telefon-Gateway allows an unauthorized user to access data marked as restricted, such as viewing or editing user profiles and application settings.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The ABB Telephone Gateway TG/S 3.2 and Busch-Jaeger 6186/11 Telefon-Gateway have improper access control implementation that allows unauthorized users to bypass authentication or authorization checks and access restricted data. Attackers can view and edit user profiles and application settings marked as restricted.

MitigationContact ABB for available firmware updates that address the access control vulnerability. If no update is available, network segmentation and restricting access to the gateway device from untrusted networks should be applied as compensating controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tg\/s3.2 FirmwareOperating system
Affected:all versions
6186\/11 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ABB or Busch-Jaeger gateway in network
    Scan your network for devices with product identification banners or HTTP response headers matching 'TG/S' or '6186/11' or 'ABB Telephone Gateway' or 'Busch-Jaeger Telefon-Gateway'
    Affected if Any device matching these product identifiers is present on the network
  2. Verify web interface accessibility
    Attempt to access the device HTTP interface from an untrusted network segment (e.g., outside the management VLAN) on typical ports 80/443
    Affected if The device web interface responds to requests from untrusted network segments without requiring VPN or jump host access
  3. Test restricted endpoint access without credentials
    Send HTTP GET requests to common restricted paths such as /user, /userlist, /settings, /admin, /configuration without providing any authentication headers or session cookies
    Affected if The device returns HTTP 200 with user profiles, application settings, or administrative data instead of redirecting to a login page or returning 401/403
  4. Check for authentication cookie or header enforcement
    Compare the HTTP response when accessing a restricted endpoint with versus without a valid session cookie or Authorization header; observe if the response differs
    Affected if Restricted endpoints return identical content regardless of authentication state (both return 200 with sensitive data)
  5. Assess network exposure
    Review firewall rules, ACLs, or network segmentation policies to determine if the gateway management interface is accessible from guest, DMZ, or other untrusted network zones
    Affected if The gateway is reachable from any network zone that contains untrusted or non-administrative systems

A user is affected if the ABB TG/S 3.2 or Busch-Jaeger 6186/11 gateway device is present and its restricted web endpoints can be accessed without authentication from any network location.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact ABB for available firmware updates that address the access control vulnerability. If no update is available, network segmentation and restricting access to the gateway device from untrusted networks should be applied as compensating controls.

Fix this in Tg\/s3.2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-19106 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data