CVE-2024-41927: Cleartext transmission of sensitive information vulnerability exists in multiple IDEC PLCs.
Noroxi assessment
Priority: Monitor (action score 18/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.15% (FIRST EPSS).
- Physical access to the device is required. 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.
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
Cleartext transmission of sensitive information vulnerability exists in multiple IDEC PLCs. If an attacker sends a specific command to PLC's serial communication port, user credentials may be obtained. As a result, the program of the PLC may be obtained, and the PLC may be manipulated.
- Published
- Sep 3, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-319
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| idec | kit-fc6a-24-kc firmware | cpe:2.3:o:idec:kit-fc6a-24-kc_firmware |
| idec | kit-fc6a-24-kc | cpe:2.3:h:idec:kit-fc6a-24-kc |
| idec | kit-fc6a-24-pc firmware | cpe:2.3:o:idec:kit-fc6a-24-pc_firmware |
| idec | kit-fc6a-24-pc | cpe:2.3:h:idec:kit-fc6a-24-pc |
| idec | kit-fc6a-24-ra firmware | cpe:2.3:o:idec:kit-fc6a-24-ra_firmware |
| idec | kit-fc6a-24-ra | cpe:2.3:h:idec:kit-fc6a-24-ra |
| idec | kit-fc6a-24-ra-hg1g firmware | cpe:2.3:o:idec:kit-fc6a-24-ra-hg1g_firmware |
| idec | kit-fc6a-24-ra-hg1g | cpe:2.3:h:idec:kit-fc6a-24-ra-hg1g |
| idec | kit-fc6a-24-ra-hg2g-5tn firmware | cpe:2.3:o:idec:kit-fc6a-24-ra-hg2g-5tn_firmware |
| idec | kit-fc6a-24-ra-hg2g-5tn | cpe:2.3:h:idec:kit-fc6a-24-ra-hg2g-5tn |
| idec | kit-fc6a-24-ra-hg2g-5tt firmware | cpe:2.3:o:idec:kit-fc6a-24-ra-hg2g-5tt_firmware |
| idec | kit-fc6a-24-ra-hg2g-5tt | cpe:2.3:h:idec:kit-fc6a-24-ra-hg2g-5tt |
and 170 more
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- idec ft1a-b12ra firmwareup to 2.41 inclusive
- idec ft1a-b24ra firmwareup to 2.41 inclusive
- idec ft1a-h12ra firmwareup to 2.41 inclusive
- idec ft1a-h12rc firmwareup to 2.41 inclusive
- idec ft1a-h24ra firmwareup to 2.41 inclusive
- idec ft1a-h24rc firmwareup to 2.41 inclusive
- idec ft1a-pc1 firmwareup to 2.41 inclusive
- idec ft1a-pc2 firmwareup to 2.41 inclusive
- idec ft1a-pc3 firmwareup to 2.41 inclusive
- idec ft1a-pm1 firmwareup to 2.41 inclusive
- idec ft9z-1a01 firmwareup to 2.41 inclusive
- idec ft9z-psp1pn05 firmwareup to 2.41 inclusive
- idec hg9z-xcm2a firmwareup to 2.41 inclusive
- idec kit-fc6a-16-kc firmwareup to 2.60 inclusive
- idec kit-fc6a-16-kd firmwareup to 2.60 inclusive
- idec kit-fc6a-16-pc firmwareup to 2.6 inclusive
- idec kit-fc6a-16-pd firmwareup to 2.60 inclusive
- idec kit-fc6a-16-ra firmwareup to 2.60 inclusive
- idec kit-fc6a-16-ra-hg1g firmwareup to 2.60 inclusive
- idec kit-fc6a-16-ra-hg2g-5tn firmwareup to 2.60 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (jpcert). Independent of NVD's CPE analysis and usually ahead of it.
IDEC Corporation FC6A Series MICROSmart All-in-One CPU module
- Ver.2.60 and earlieraffected
IDEC Corporation FC6A Series MICROSmart Plus CPU module
- Ver.2.40 and earlieraffected
IDEC Corporation FC6B Series MICROSmart All-in-One CPU module
- Ver.2.60 and earlieraffected
IDEC Corporation FC6B Series MICROSmart Plus CPU module
- Ver.2.60 and earlieraffected
IDEC Corporation FT1A Series SmartAXIS Pro/Lite
- Ver.2.41 and earlieraffected
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 researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
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).
Technical details
Attack conditions
- Physical access to the device is required.
- 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
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-319 · Cleartext Transmission of Sensitive InformationCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
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
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.