CVE-2003-0143
Published Sep 1, 2004 · Updated Oct 23, 2026
Original summary
Normalized public record · Updated Oct 23, 2026
The pop_msg function in qpopper 4.0.x before 4.0.5fc2 does not null terminate a message buffer after a call to Qvsnprintf, which could allow authenticated users to execute arbitrary code via a buffer overflow in a mdef command with a long macro name.
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
The pop_msg function in qpopper 4.0.x before 4.0.5fc2 does not null terminate a message buffer after a call to Qvsnprintf, which could allow authenticated users to execute arbitrary code via a buffer overflow in a mdef command with a long macro name.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- 40%
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- GLSA-200303-12 ↗
- 7058 ↗
- Security advisory ↗
- 20030310 QPopper 4.0.x buffer overflow vulnerability ↗
- 20030314 [OpenPKG-SA-2003.018] OpenPKG Security Advisory (qpopper) ↗
- DSA-259 ↗
- qpopper-popmsg-macroname-bo(11516) ↗
- 20030312 Re: QPopper 4.0.x buffer overflow vulnerability ↗
Record history
Published Sep 1, 2004 · Last refreshed Oct 23, 2026