CVE-2003-0054
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 · uneditedApple Darwin Streaming Administration Server 4.1.2 and QuickTime Streaming Server 4.1.1 allows remote attackers to execute certain code via a request to port 7070 with the script in an argument to the rtsp DESCRIBE method, which is inserted into a log file and executed when the log is viewed using a browser.
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 confidenceA log injection vulnerability in Apple Darwin Streaming Administration Server 4.1.2 and QuickTime Streaming Server 4.1.1 allows remote attackers to inject malicious script code via the RTSP DESCRIBE method to port 7070. The injected script is written to a log file and executes when viewed through a web browser, potentially leading to session hijacking or further attacks against administrators viewing the logs.
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= 4.1.2= 4.1.1CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Identify if Darwin Streaming Server or QuickTime Streaming Server is installedCheck for the presence of the streaming server software on the system. Look for processes named 'DarwinStreamingServer' or 'QuickTimeStreamingServer', or check common installation directories.Affected if Either Darwin Streaming Server or QuickTime Streaming Server is present on the system
-
Determine the installed versionCheck the version of the installed streaming server. For Darwin Streaming Server, this is typically displayed in the admin web interface or can be found in server version files.Affected if The installed version is exactly 4.1.2 for Darwin Streaming Server or exactly 4.1.1 for QuickTime Streaming Server
-
Verify if RTSP service on port 7070 is accessibleCheck if the RTSP service is listening on port 7070. This can be done using netstat or similar network tools to confirm the service is running and accessible.Affected if The RTSP service on port 7070 is active and reachable from network locations
-
Confirm web-based admin log viewing is enabledCheck if the streaming server admin web interface is enabled and accessible, particularly the log viewing functionality.Affected if The admin web interface is enabled and logs can be viewed through a browser
A system is affected if it runs Darwin Streaming Server 4.1.2 or QuickTime Streaming Server 4.1.1 with both the RTSP service on port 7070 accessible and web-based log viewing enabled.
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 the latest version of Darwin Streaming Server/QuickTime Streaming Server. Alternatively, disable browser-based log viewing, implement strict log access controls, and ensure logs are viewed in plain text format rather than through any web interface.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0054 — 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-2003-0054 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