CVE-2025-1712: Arbitrary file write with vcrtrace

Published May 21, 2025
·
Updated

Argument injection in special agent configuration in Checkmk <2.4.0p1, <2.3.0p32, <2.2.0p42 and 2.1.0 allows authenticated attackers to write arbitrary files

Affected Software

102 affected components
Checkmk Checkmk<2.4.0p1
Checkmk Checkmk<2.3.0p32
Checkmk Checkmk<2.2.0p42
Checkmk Checkmk
Checkmk Checkmk<2.2.0
Checkmk Checkmk=2.2.0
Checkmk Checkmk=2.2.0-b1
Checkmk Checkmk=2.2.0-b2
Checkmk Checkmk=2.2.0-b3
Checkmk Checkmk=2.2.0-b4
Checkmk Checkmk=2.2.0-b5
Checkmk Checkmk=2.2.0-b6
Checkmk Checkmk=2.2.0-b7
Checkmk Checkmk=2.2.0-b8
Checkmk Checkmk=2.2.0-i1
Checkmk Checkmk=2.2.0-p1
Checkmk Checkmk=2.2.0-p10
Checkmk Checkmk=2.2.0-p11
Checkmk Checkmk=2.2.0-p12
Checkmk Checkmk=2.2.0-p13
Checkmk Checkmk=2.2.0-p14
Checkmk Checkmk=2.2.0-p15
Checkmk Checkmk=2.2.0-p16
Checkmk Checkmk=2.2.0-p17
Checkmk Checkmk=2.2.0-p18
Checkmk Checkmk=2.2.0-p19
Checkmk Checkmk=2.2.0-p2
Checkmk Checkmk=2.2.0-p20
Checkmk Checkmk=2.2.0-p21
Checkmk Checkmk=2.2.0-p22
Checkmk Checkmk=2.2.0-p23
Checkmk Checkmk=2.2.0-p24
Checkmk Checkmk=2.2.0-p25
Checkmk Checkmk=2.2.0-p26
Checkmk Checkmk=2.2.0-p27
Checkmk Checkmk=2.2.0-p28
Checkmk Checkmk=2.2.0-p29
Checkmk Checkmk=2.2.0-p3
Checkmk Checkmk=2.2.0-p30
Checkmk Checkmk=2.2.0-p31
Checkmk Checkmk=2.2.0-p32
Checkmk Checkmk=2.2.0-p33
Checkmk Checkmk=2.2.0-p34
Checkmk Checkmk=2.2.0-p35
Checkmk Checkmk=2.2.0-p36
Checkmk Checkmk=2.2.0-p37
Checkmk Checkmk=2.2.0-p38
Checkmk Checkmk=2.2.0-p39
Checkmk Checkmk=2.2.0-p4
Checkmk Checkmk=2.2.0-p40
Checkmk Checkmk=2.2.0-p41
Checkmk Checkmk=2.2.0-p5
Checkmk Checkmk=2.2.0-p6
Checkmk Checkmk=2.2.0-p7
Checkmk Checkmk=2.2.0-p8
Checkmk Checkmk=2.2.0-p9
Checkmk Checkmk=2.3.0
Checkmk Checkmk=2.3.0
Checkmk Checkmk=2.3.0-b1
Checkmk Checkmk=2.3.0-b2
Checkmk Checkmk=2.3.0-b3
Checkmk Checkmk=2.3.0-b4
Checkmk Checkmk=2.3.0-b5
Checkmk Checkmk=2.3.0-b6
Checkmk Checkmk=2.3.0-p1
Checkmk Checkmk=2.3.0-p10
Checkmk Checkmk=2.3.0-p11
Checkmk Checkmk=2.3.0-p12
Checkmk Checkmk=2.3.0-p13
Checkmk Checkmk=2.3.0-p14
Checkmk Checkmk=2.3.0-p15
Checkmk Checkmk=2.3.0-p16
Checkmk Checkmk=2.3.0-p17
Checkmk Checkmk=2.3.0-p18
Checkmk Checkmk=2.3.0-p19
Checkmk Checkmk=2.3.0-p2
Checkmk Checkmk=2.3.0-p20
Checkmk Checkmk=2.3.0-p21
Checkmk Checkmk=2.3.0-p22
Checkmk Checkmk=2.3.0-p23
Checkmk Checkmk=2.3.0-p24
Checkmk Checkmk=2.3.0-p25
Checkmk Checkmk=2.3.0-p26
Checkmk Checkmk=2.3.0-p27
Checkmk Checkmk=2.3.0-p28
Checkmk Checkmk=2.3.0-p29
Checkmk Checkmk=2.3.0-p3
Checkmk Checkmk=2.3.0-p30
Checkmk Checkmk=2.3.0-p31
Checkmk Checkmk=2.3.0-p4
Checkmk Checkmk=2.3.0-p5
Checkmk Checkmk=2.3.0-p6
Checkmk Checkmk=2.3.0-p7
Checkmk Checkmk=2.3.0-p8
Checkmk Checkmk=2.3.0-p9
Checkmk Checkmk=2.4.0
Checkmk Checkmk=2.4.0-b1
Checkmk Checkmk=2.4.0-b2
Checkmk Checkmk=2.4.0-b3
Checkmk Checkmk=2.4.0-b4
Checkmk Checkmk=2.4.0-b5
Checkmk Checkmk=2.4.0-b6

Event History

May 21, 2025
CVE Published
via MITRE·09:10 AM
Data Sourced
via MITRE·09:10 AM
DescriptionWeakness
Data Sourced
via NVD·09:15 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-1712?

CVE-2025-1712 has been rated as a high severity vulnerability due to its potential for authenticated attackers to write arbitrary files.

2

How do I fix CVE-2025-1712?

To fix CVE-2025-1712, update Checkmk to version 2.4.0p1 or higher, 2.3.0p32 or higher, or 2.2.0p42 or higher.

3

What types of systems are affected by CVE-2025-1712?

CVE-2025-1712 affects Checkmk versions earlier than 2.4.0p1, 2.3.0p32, and 2.2.0p42.

4

Can CVE-2025-1712 be exploited remotely?

CVE-2025-1712 requires authenticated access, thus potential exploitation is limited to users with valid credentials.

5

What impact does CVE-2025-1712 have on system security?

CVE-2025-1712 allows authenticated attackers to compromise system integrity by writing arbitrary files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203