CVE-2004-2238: Medium severity Inter7 Vpopmail \(vchkpw\) vulnerability

Published Dec 31, 2004
·
Updated

DISPUTED Format string vulnerability in vsybase.c in vpopmail 5.4.2 and earlier has unknown impact and attack vectors. NOTE: in a followup post, it was observed that the source code used constants that, when compiled, became static format strings. Thus this is not a vulnerability.

Affected Software

70 affected components
Inter7 Vpopmail \(vchkpw\)=3.4.11e
Inter7 Vpopmail \(vchkpw\)=3.4.1
Inter7 Vpopmail \(vchkpw\)=5.2.1
Inter7 Vpopmail \(vchkpw\)=4.9.10
Inter7 Vpopmail \(vchkpw\)=5.3.30
Inter7 Vpopmail \(vchkpw\)=3.4.6
Inter7 Vpopmail \(vchkpw\)=3.4.11
Inter7 Vpopmail \(vchkpw\)=3.4.2
Inter7 Vpopmail \(vchkpw\)=4.10
Inter7 Vpopmail \(vchkpw\)=3.4.10
Inter7 Vpopmail \(vchkpw\)=4.9
Inter7 Vpopmail \(vchkpw\)=3.4.8
Inter7 Vpopmail \(vchkpw\)=4.6
Inter7 Vpopmail \(vchkpw\)=5.3.28
Inter7 Vpopmail \(vchkpw\)=5.3.27
Inter7 Vpopmail \(vchkpw\)=5.3.22
Inter7 Vpopmail \(vchkpw\)=5.3.21
Inter7 Vpopmail \(vchkpw\)=5.3.26
Inter7 Vpopmail \(vchkpw\)=5.4
Inter7 Vpopmail \(vchkpw\)=3.4.5
Inter7 Vpopmail \(vchkpw\)=4.7
Inter7 Vpopmail \(vchkpw\)=3.4.9
Inter7 Vpopmail \(vchkpw\)=5.3.29
Inter7 Vpopmail \(vchkpw\)=3.4.7
Inter7 Vpopmail \(vchkpw\)=5.4.1
Inter7 Vpopmail \(vchkpw\)=5.3.24
Inter7 Vpopmail \(vchkpw\)=5.3.23
Inter7 Vpopmail \(vchkpw\)=5.3.25
Inter7 Vpopmail \(vchkpw\)=3.4.3
Inter7 Vpopmail \(vchkpw\)=4.8
Inter7 Vpopmail \(vchkpw\)=5.3.20
Inter7 Vpopmail \(vchkpw\)=3.4.4
Inter7 Vpopmail \(vchkpw\)=5.4.2
Inter7 Vpopmail \(vchkpw\)=4.5
Inter7 Vpopmail \(vchkpw\)=5.2.2
Inter7 Vpopmail \(vchkpw\)=3.4.1
Inter7 Vpopmail \(vchkpw\)=3.4.2
Inter7 Vpopmail \(vchkpw\)=3.4.3
Inter7 Vpopmail \(vchkpw\)=3.4.4
Inter7 Vpopmail \(vchkpw\)=3.4.5
Inter7 Vpopmail \(vchkpw\)=3.4.6
Inter7 Vpopmail \(vchkpw\)=3.4.7
Inter7 Vpopmail \(vchkpw\)=3.4.8
Inter7 Vpopmail \(vchkpw\)=3.4.9
Inter7 Vpopmail \(vchkpw\)=3.4.10
Inter7 Vpopmail \(vchkpw\)=3.4.11
Inter7 Vpopmail \(vchkpw\)=3.4.11e
Inter7 Vpopmail \(vchkpw\)=4.5
Inter7 Vpopmail \(vchkpw\)=4.6
Inter7 Vpopmail \(vchkpw\)=4.7
Inter7 Vpopmail \(vchkpw\)=4.8
Inter7 Vpopmail \(vchkpw\)=4.9
Inter7 Vpopmail \(vchkpw\)=4.9.10
Inter7 Vpopmail \(vchkpw\)=4.10
Inter7 Vpopmail \(vchkpw\)=5.2.1
Inter7 Vpopmail \(vchkpw\)=5.2.2
Inter7 Vpopmail \(vchkpw\)=5.3.20
Inter7 Vpopmail \(vchkpw\)=5.3.21
Inter7 Vpopmail \(vchkpw\)=5.3.22
Inter7 Vpopmail \(vchkpw\)=5.3.23
Inter7 Vpopmail \(vchkpw\)=5.3.24
Inter7 Vpopmail \(vchkpw\)=5.3.25
Inter7 Vpopmail \(vchkpw\)=5.3.26
Inter7 Vpopmail \(vchkpw\)=5.3.27
Inter7 Vpopmail \(vchkpw\)=5.3.28
Inter7 Vpopmail \(vchkpw\)=5.3.29
Inter7 Vpopmail \(vchkpw\)=5.3.30
Inter7 Vpopmail \(vchkpw\)=5.4
Inter7 Vpopmail \(vchkpw\)=5.4.1
Inter7 Vpopmail \(vchkpw\)=5.4.2

Remediation

Patch Available

http://www.osvdb.org/9147

Patch Available

http://www.securityfocus.com/bid/10962

Event History

Dec 31, 2004
CVE Published
05:00 AM
Disputed
05:00 AM
Jul 17, 2005
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2004-2238?

The severity of CVE-2004-2238 is currently disputed and considered low due to the nature of the vulnerability.

2

What versions of Vpopmail are affected by CVE-2004-2238?

Vpopmail versions 5.4.2 and earlier are affected by CVE-2004-2238.

3

How do I fix CVE-2004-2238?

Currently, there is no necessary fix for CVE-2004-2238 as the vulnerability has been disputed, indicating it may not exist.

4

Is CVE-2004-2238 a confirmed vulnerability in Vpopmail?

CVE-2004-2238 is disputed and may not be a confirmed vulnerability in Vpopmail.

5

What is a format string vulnerability in relation to CVE-2004-2238?

A format string vulnerability like CVE-2004-2238 involves improper handling of format strings in programming, but its impact is unclear in this case.

Company

Resources

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