NVD / CVE Program· CNA Toshiba

CVE-2024-27159: Hardcoded password used to encrypt logs

Noroxi assessment

Priority: Monitor (action score 24/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

All the Toshiba printers contain a shell script using the same hardcoded key to encrypt logs. An attacker can decrypt the encrypted files using the hardcoded key. 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.

MediumCVSS 6.2 · v3.1—No exploit No fix recorded

Hard-coded credentials

Published: Jun 14, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 17th percentile
CWE: CWE-798

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 24 / 40 · 6.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Toshiba: 6.2; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Toshiba). Independent of NVD's CPE analysis and usually ahead of it.

Toshiba Tec Corporation Toshiba Tec e-Studio multi-function peripheral (MFP)
- see the reference URLaffected

Same product

toshiba tec corporation: all records

Other highest-scoring records for the same primary product.

CVE-2024-27172Remote Code Execution
47Plan
CVE-2024-27173Remote Command program allows an attacker to get Remote Code Execution by overwriting existing Python files containing executable code.
40Plan
CVE-2024-27174Remote Command program allows an attacker to get Remote Code Execution.
39Monitor

Published before and after this one in the same product

← EarlierCVE-2024-27157Jun 14, 2024 · Leak of authentication sessions in secure logs
27Monitor
← EarlierCVE-2024-27158Jun 14, 2024 · Hardcoded root password
29Monitor
Later →CVE-2024-27160Jun 14, 2024 · Hardcoded password used to encrypt logs and use of weak cipher
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

We expresses its gratitude to Pierre Barre for reporting relevant security vulnerabilities for our products.finder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-271700 days apartHardcoded credentials for WebDAV access
29Monitor
CVE-2024-271680 days apartHardcoded keys used to generate authentication cookies
28Monitor
CVE-2024-271600 days apartHardcoded password used to encrypt logs and use of weak cipher
24Monitor
CVE-2024-271610 days apartHardcoded password used to encrypt files
24Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0709 · Jun 14, 2024(Toshiba Yazıcıları Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Someone with local access to the system can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Local
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-798 · Use of Hard-coded Credentials

CVSS vector

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

nvd-secondary

Root cause

For convenience in support or manufacturing, an account that is identical on every device is embedded in the software. Credentials learned from one device work on all of them.

The bug in code

The whole CWE-798 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const SUPPORT_USER = "support";
2const SUPPORT_PASS = "hardcoded-password";

Fixed

1const creds = await provisioning.deviceCredentials(deviceId);
2if (creds.mustRotate) await forcePasswordChange(deviceId);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

seclists.org/fulldisclosure/2024/Jul/1

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records