CVE-1999-1526
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 · uneditedAuto-update feature of Macromedia Shockwave 7 transmits a user's password and hard disk information back to Macromedia.
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 confidenceThe auto-update feature in Macromedia Shockwave 7 has a privacy vulnerability where it transmits user passwords and hard disk information back to Macromedia servers during the update process, exposing sensitive local system data.
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= 7.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
- 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.
-
Verify if Macromedia Shockwave 7 is installedCheck the installed programs list in Control Panel (Windows) or Applications folder (Mac) for Macromedia Shockwave or search for shockwave files in the system. In browsers, check the plugin list for Shockwave Flash Plugin.Affected if Macromedia Shockwave 7 is present on the system
-
Confirm the installed version is 7.0Right-click on Shockwave content in a browser and view plugin details, or check the program's properties/version info in the installed files. Compare the version number against the affected range (= 7.0).Affected if The installed version is exactly 7.0
-
Locate the auto-update configurationSearch for Shockwave-related update files or configuration in the application data folders, browser plugin settings, or Windows registry for Shockwave update settings. Look for files named similar to 'swupdate' or update configuration in the Shockwave installation directory.Affected if Auto-update feature configuration files exist and the update mechanism is present and enabled
A system is affected if Macromedia Shockwave version 7.0 is installed with its auto-update feature enabled, as the vulnerability requires both the specific version and an active update mechanism to transmit data.
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 dataDisable or remove the Macromedia Shockwave 7 auto-update feature. Since this is legacy software from 1999, organizations should assess whether Shockwave is still in use and migrate to modern alternatives if possible.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1526 — 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-1999-1526 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