CVE-2025-0101: WAGO: Year 2038 problem
First published: Wed Apr 16 2025(Updated: )
A low privileged user can set the date of the devices to the 19th of January 2038 an therefore exceed the 32-Bit time limit. This causes some functions to work unexpected or stop working at all. Both during runtime and after a restart.
Credit: info@cert.vde.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WAGO Year 2038 problem |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-0101?
CVE-2025-0101 is considered a low severity vulnerability affecting device date settings.
What is the impact of CVE-2025-0101?
CVE-2025-0101 allows a low privileged user to change the device date to January 19, 2038, causing functions to fail or behave unexpectedly.
How do I fix CVE-2025-0101?
To resolve CVE-2025-0101, ensure that devices have access controls preventing low-privileged users from changing system dates.
Which software is affected by CVE-2025-0101?
CVE-2025-0101 affects WAGO devices that are vulnerable to the Year 2038 problem.
What should be monitored due to CVE-2025-0101?
It is important to monitor the device functionality and access logs for suspicious date changes related to CVE-2025-0101.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/references
- agent/first-publish-date
- agent/type
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/source
- agent/author
- agent/tags
- agent/severity
- agent/event
- vendor/wago
- canonical/wago year 2038 problem