CVE-2009-1792
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 · uneditedThe system.openURL function in StoneTrip Ston3D StandalonePlayer (aka S3DPlayer StandAlone) 1.6.2.4 and 1.7.0.1 and WebPlayer (aka S3DPlayer Web) 1.6.0.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the first argument (the sURL argument).
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 confidenceCommand injection vulnerability in the system.openURL function of StoneTrip S3DPlayer StandalonePlayer (versions 1.6.2.4, 1.7.0.1) and WebPlayer (version 1.6.0.0). Attackers can execute arbitrary OS commands by embedding shell metacharacters in the sURL argument passed to this function.
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= 1.6.2.4= 1.7.0.1= 1.6.0.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 installed S3DPlayer productLook for StoneTrip S3DPlayer executables or browser plugins. On Windows, check Program Files for 'S3DPlayer', 'S3D' or 'StoneTrip' folders. On Linux/Mac, check typical application directories. For WebPlayer, check browser plugins/extensions for S3D-related components.Affected if StoneTrip S3DPlayer Standalone or WebPlayer is found on the system
-
Determine the exact version numberRight-click the StandalonePlayer executable, select Properties, then Details tab to view File Version. For WebPlayer, check the DLL/plugin version in the browser's extension manager or the plugin file properties.Affected if Version matches 1.6.2.4 or 1.7.0.1 (Standalone) or 1.6.0.0 (Web)
-
Locate scripts using system.openURLSearch project directories and S3D content files (typically .s3d or .s3dp files) for occurrences of 'system.openURL' or 'openURL(' function calls.Affected if Code calling system.openURL function is present in deployed content
-
Verify sURL parameter exposureExamine the identified system.openURL calls and trace whether the sURL argument receives input from external sources (URL parameters, user input, file contents, network data).Affected if The sURL parameter accepts or processes untrusted external input containing potential shell metacharacters
A user is affected if they have StandalonePlayer versions 1.6.2.4 or 1.7.0.1, or WebPlayer version 1.6.0.0, AND their content/scripts call system.openURL with externally-sourced URL data that could contain shell metacharacters.
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 dataIf the software is still in use, upgrade to a patched version if available; otherwise migrate to a supported alternative or decommission the affected installation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1792 — 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-2009-1792 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