dbcve.org
TransitmasterApplication · Trapezegroup

CVE-2017-14943

HIGH · 7.5 CVSS v3.0 Published 2017-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Trapeze TransitMaster is vulnerable to information disclosure (emails / hashed passwords) via a modified userID field in JSON data to ManageSubscriber.aspx/GetSubscriber. NOTE: this software is independently deployed at multiple municipal transit systems; it is not found exclusively on the "webwatch.(REDACTED).com" server mentioned in the reference.

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

Trapeze TransitMaster's ManageSubscriber.aspx/GetSubscriber endpoint allows unauthenticated or unauthorized users to retrieve sensitive subscriber information by modifying the userID parameter in JSON requests. The endpoint returns email addresses and hashed passwords without proper authorization validation, enabling information disclosure to any attacker who can craft appropriate JSON requests.

MitigationImplement proper authentication and authorization checks on the GetSubscriber endpoint to verify the requesting user has rights to access the requested subscriber data. Validate user sessions and enforce role-based access controls before returning any sensitive information.

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
TransitmasterApplication
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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 if Trapeze TransitMaster is installed
    Check for the presence of the TransitMaster web application by looking for 'ManageSubscriber.aspx' in the web root directory or by enumerating exposed web paths on the server.
    Affected if The TransitMaster web application files exist on the system.
  2. Locate the GetSubscriber endpoint
    Identify the full URL path to the GetSubscriber endpoint, typically found at /ManageSubscriber.aspx/GetSubscriber within the TransitMaster application directory.
    Affected if The endpoint path /ManageSubscriber.aspx/GetSubscriber is accessible on the web server.
  3. Test endpoint accessibility without authentication
    Send a crafted GET or POST request to the GetSubscriber endpoint without providing any session token, authentication credentials, or cookies.
    Affected if The endpoint accepts and processes requests without requiring valid authentication.
  4. Verify parameter manipulation vulnerability
    Send a JSON request to the endpoint with a userID parameter value different from the currently authenticated user's ID, observing whether the server returns data for the requested userID without validating authorization.
    Affected if The endpoint returns subscriber data for arbitrary userID values without proper authorization checks.
  5. Confirm sensitive data exposure
    Examine the response from the GetSubscriber endpoint to determine if it contains sensitive fields such as email addresses and hashed passwords without role-based access control validation.
    Affected if The endpoint returns email addresses and password hashes to unauthenticated or unauthorized users.

If the TransitMaster ManageSubscriber.aspx/GetSubscriber endpoint is accessible and returns subscriber email addresses or password hashes when queried with arbitrary userID values without requiring valid authentication or authorization, the environment is affected by CVE-2017-14943.

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 authentication and authorization checks on the GetSubscriber endpoint to verify the requesting user has rights to access the requested subscriber data. Validate user sessions and enforce role-based access controls before returning any sensitive information.

Fix this in Transitmaster Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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