CVE-2004-0743
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSafari in Mac OS X before 10.3.5, after sending form data using the POST method, may re-send the data to a GET method URL if that URL is redirected after the POST data and the user uses the forward or backward buttons, which may cause an information leak.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Safari on Mac OS X before 10.3.5, when form data is submitted via POST and the server redirects to a GET URL, using the browser's forward or backward buttons can cause Safari to re-send the POST data to the GET endpoint, potentially leaking sensitive information to an unintended location.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.2= 10.2.1= 10.2.2= 10.2.3= 10.2.4= 10.2.5= 10.2.6= 10.2.7= 10.2.8= 10.3= 10.3.1= 10.3.2= 10.2= 10.2.1= 10.2.2= 10.2.3= 10.2.4= 10.2.5= 10.2.6= 10.2.7= 10.2.8= 10.3= 10.3.1= 10.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the Mac OS X versionGo to Apple menu > About This Mac to view the installed Mac OS X version numberAffected if The version is 10.2.x or 10.3.x through 10.3.2 (any of the listed affected versions)
-
Confirm Safari is the browser in useVerify that Safari is the web browser being used to access web applications with form-based data submissionAffected if Safari is the browser and the OS version is in the affected range
-
Identify POST form submissions with server redirectsReview web application traffic: submit a form via POST method and check if the server returns a redirect (HTTP 301/302) to a GET-accessible URLAffected if The application uses POST for forms and the server redirects to a GET URL, creating the condition where forward/back button usage can resend POST data to the GET endpoint
You are affected if running Mac OS X 10.2.x or 10.3.x through 10.3.2 and using Safari to interact with web applications that submit sensitive data via POST and receive server redirects to GET URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Mac OS X 10.3.5 or later which contains the patched Safari version. For custom web applications, ensure servers reject POST data on GET endpoints and implement proper cache-control headers to prevent browser caching of sensitive responses.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0743 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2004-0743 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data