The hard drives of the device are not encrypted using a full volume encryption feature such as BitLocker.
The hard drives of the device are not encrypted using a full volume encryption feature such as BitLocker. This allows an attacker with physical access to the device to use an alternative operating system to interact with the hard drives, completely circumventing the Windows login. The attacker can read from and write to all files on the hard drives.
- Published
- Jul 3, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-312
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.8
- CNA · SICK AG
- 7.6
- 0.8 point gap
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| endress | meac300-fnade4 firmware | cpe:2.3:o:endress:meac300-fnade4_firmware |
| endress | meac300-fnade4 | cpe:2.3:h:endress:meac300-fnade4 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- endress meac300-fnade4 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (SICK AG). Independent of NVD's CPE analysis and usually ahead of it.
Endress+Hauser Endress+Hauser MEAC300-FNADE4
- vers:all/*affected
Same product
endress: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-27456The SMB server's login mechanism does not implement sufficient measures to prevent multiple failed authentication attempts within a short ti39Monitor
- CVE-2025-27449The MEAC300-FNADE4 does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, maki39Monitor
- CVE-2025-1710The maxView Storage Manager does not implement sufficient measures to prevent multiple failed authentication attempts within a short time fr39Monitor
- CVE-2025-27459The VNC application stores its passwords encrypted within the registry but uses DES for encryption.30Monitor
- CVE-2025-27458The VNC authentication mechanism bases on a challenge-response system where both server and client use the same password for encryption.30Monitor
- CVE-2025-27457All communication between the VNC server and client(s) is unencrypted.30Monitor
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-312 · Cleartext Storage of Sensitive InformationCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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)
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.first.org/cvss/calculator/3.1
- sick.com/psirt
- www.cisa.gov/resources-tools/resources/ics-recommended-practices
- www.endress.com
- www.sick.com/.well-known/csaf/white/2025/sca-2025-0008.json
- www.sick.com/.well-known/csaf/white/2025/sca-2025-0008.pdf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.