CVE-2025-64642
BaseFortify
Publication date: 2025-12-02
Last updated on: 2025-12-04
Assigner: ICS-CERT
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nmis | biodose | * |
| nmis | biodose | 22.02 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-732 | The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists because the installation directory paths of NMIS/BioDose V22.02 and earlier versions have insecure file permissions by default. This can allow users on client workstations to modify the program executables and libraries under certain deployment scenarios.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing unauthorized users on client workstations to modify critical program executables and libraries. This can lead to potential compromise of the software's integrity, unauthorized code execution, or disruption of normal operations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the file permissions of the NMIS/BioDose installation directory and its executables and libraries to see if they are insecurely set, allowing modification by unauthorized users. Specific commands depend on the operating system, but for Unix-like systems, you can use commands like 'ls -l' to list permissions and 'stat' to get detailed file permission information on the installation directory and its files.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include correcting the file permissions of the NMIS/BioDose installation directory and its executables and libraries to restrict modification rights only to authorized users. This typically involves setting stricter permissions to prevent client workstation users from modifying program files.