dbcve.org
JetselectApplication · Jetstream

CVE-2019-13023

MEDIUM · 6.5 CVSS v3.1 Published 2020-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An issue was discovered in all versions of Bond JetSelect. Within the JetSelect Application, the web interface hides RADIUS secrets, WPA passwords, and SNMP strings from 'non administrative' users using HTML 'password field' obfuscation. By using Developer tools or similar, it is possible to change the obfuscation so that the credentials are visible.

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 · high confidence

The JetSelect web application uses HTML password field obfuscation to hide sensitive credentials (RADIUS secrets, WPA passwords, SNMP strings) from non-administrative users. This is purely client-side protection that can be bypassed by using browser Developer tools to change the input type from 'password' to 'text', allowing any authenticated user to view these credentials in plain text.

MitigationImplement proper server-side authorization so that sensitive credentials are not transmitted to non-admin users at all. Admin users who legitimately need to view credentials should be authenticated through a secure mechanism, and credentials should be stored encrypted with proper access 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
JetselectApplication
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 JetSelect installation
    Check for the Jetstream Jetselect web application in your environment by reviewing installed software, web server directories, or network scans for Jetselect services
    Affected if JetSelect web application is present
  2. Verify password-type input fields
    Log into the JetSelect web interface and navigate to pages containing sensitive configuration (RADIUS secrets, WPA passwords, SNMP strings). Inspect the HTML source or use browser Developer tools to check if credential fields use input type='password'
    Affected if Sensitive credential fields use type='password' HTML input attribute
  3. Test non-admin access to credential fields
    Log in as a non-administrative user and navigate to pages displaying sensitive credentials. Use browser Developer tools to change input type from 'password' to 'text' and observe if plain-text credentials become visible
    Affected if Non-admin users can view plain-text credentials after changing input type to text
  4. Check credential transmission to non-admin users
    Use browser Developer tools or a proxy to intercept HTTP responses when a non-admin user loads credential configuration pages. Inspect if credential values are present in the response in any form (obfuscated or not)
    Affected if Sensitive credentials are transmitted to non-admin users in the HTML response

Your environment is affected if the JetSelect web application is running and sensitive credentials are accessible to non-administrative users through password-type input fields that can be changed to text.

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

Implement proper server-side authorization so that sensitive credentials are not transmitted to non-admin users at all. Admin users who legitimately need to view credentials should be authenticated through a secure mechanism, and credentials should be stored encrypted with proper access controls.

Fix this in Jetselect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-13023 — 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-13023 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