dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2024-27163

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Toshiba printers will display the password of the admin user in clear-text and additional passwords when sending 2 specific HTTP requests to the internal API. An attacker stealing the cookie of an admin or abusing a XSS vulnerability can recover this password in clear-text and compromise the printer. This vulnerability can be executed in combination with other vulnerabilities and difficult to execute alone. So, the CVSS score for this vulnerability alone is lower than the score listed in the "Base Score" of this vulnerability. For detail on related other vulnerabilities, please ask to the below contact point. https://www.toshibatec.com/contacts/products/ As for the affected products/models/versions, see the reference URL.

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

Toshiba printers contain an internal API vulnerability where two specific HTTP requests return the admin user's password in clear-text along with additional passwords. Exploitation requires either stealing an admin session cookie or chaining with a separate XSS vulnerability to access these API endpoints.

MitigationRestrict access to the internal API endpoints and implement proper authentication/authorization checks. Additionally, remediate any XSS vulnerabilities and protect admin session cookies to prevent credential theft.

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

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Toshiba printer model and firmware version
    Access the printer web interface or check the device info page, typically at /webgl/local/ or through the printer's status/diagnostic page. Note the exact model number and firmware version.
    Affected if The device is a Toshiba printer and the firmware version falls within any known affected ranges or is unknown/unpatched.
  2. Verify admin session cookie configuration
    Log into the printer admin interface and examine the session cookie set by the server. Check if the cookie has HttpOnly and Secure flags set, and observe whether the session token is exposed in URLs or can be accessed via client-side scripts.
    Affected if Admin session cookies lack HttpOnly flag or are accessible via XSS, allowing credential theft.
  3. Test internal API endpoint accessibility
    Send two HTTP GET requests to common Toshiba printer internal API endpoints (typically /api/admin/ or /webgl/local/ endpoints that expose user/password data). Observe if the responses contain clear-text passwords without requiring elevated authentication beyond a valid session cookie.
    Affected if The internal API returns admin passwords in clear-text to any authenticated session without additional authorization verification.
  4. Check for existing XSS vulnerabilities
    Review any web application scanning results or manually test input fields in the printer web interface for reflected or stored XSS. Common test inputs: <script>alert(1)</script> injected into printer name, network settings, or user profile fields.
    Affected if XSS vulnerabilities exist that could be chained to steal admin session cookies and access the internal API.

Your Toshiba printer is affected if the internal API endpoints return admin passwords in clear-text to any authenticated user, especially if session cookies lack HttpOnly protection or XSS vulnerabilities exist that could facilitate cookie theft.

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

Restrict access to the internal API endpoints and implement proper authentication/authorization checks. Additionally, remediate any XSS vulnerabilities and protect admin session cookies to prevent credential theft.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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