VulnerabilityPublished 15 Jan 2024Updated 3 Jun 2025

CVE-2024-22028: THREE R SOLUTION CORP. JAPAN 3R-TMC01 · Insufficient Verification of Data Authenticity

Affects THREE R SOLUTION CORP. JAPAN 3R-TMC01Source CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should implement strict physical security controls to prevent unauthorized access to the 3R-TMC01 devices, including secure mounting, restricted access areas, and surveillance. Until official patches or firmware updates are released by THREE R SOLUTION CORP., organizations should inventory all affected devices and assess the sensitivity of the data stored on them. If possible, disable or limit internal data storage features or encrypt stored data using external means. Additionally, organizations should request detailed technical documentation and security guidance from the vendor to understand the data storage mechanisms and potential risks. Regular physical inspections and tamper-evident seals can help detect unauthorized access attempts. For high-risk environments, consider replacing affected devices with alternatives that provide stronger data protection and transparency. Finally, maintain an incident response plan that includes procedures for physical device compromise and data leakage scenarios.

Description

Insufficient technical documentation issue exists in thermal camera TMC series all firmware versions. The user of the affected product is not aware of the internally saved data. By accessing the affected product physically, an attacker may retrieve the internal data.

Impact

For European organizations, the primary impact of this vulnerability is the potential unauthorized disclosure of sensitive data stored internally on the 3R-TMC01 thermal cameras. These devices may be used in critical infrastructure monitoring, industrial environments, or security-sensitive locations. If an attacker gains physical access to the device, they could extract confidential thermal imaging data or other internal information, potentially exposing operational details or sensitive environmental conditions. This could lead to privacy violations, industrial espionage, or compromise of security monitoring capabilities. While the vulnerability does not allow remote exploitation or disruption of device functionality, the confidentiality breach risk is significant in environments where physical security is not tightly controlled. Organizations relying on these thermal cameras for security or operational monitoring should be aware that physical device theft or tampering could lead to data leakage. The impact is heightened in sectors with strict data protection regulations such as GDPR, where unauthorized data disclosure can lead to regulatory penalties and reputational damage.

References

Community reviews

Loading reviews…