CVE-2010-2219
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 · uneditedUnspecified vulnerability in Adobe Flash Media Server (FMS) before 3.0.6, and 3.5.x before 3.5.4, allows attackers to cause a denial of service (memory consumption) via unknown vectors.
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 · moderate confidenceAdobe Flash Media Server versions before 3.0.6 and 3.5.x before 3.5.4 contain an unspecified vulnerability that allows remote attackers to cause denial of service through memory consumption. The exact attack vector and vulnerability type are not detailed in the advisory.
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<= 3.0.5= 2.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4all versions= 2.0.4CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 installed Adobe Flash Media Server versionCheck the version file or service information. On Windows, check the 'fms' service version via services.msc or look in the installation directory (typically Program Files\Adobe\Flash Media Server\) for a version manifest. On Linux, check /opt/adobe/fms/ for version files or run 'fmsadmin --version' if available.Affected if The installed version is 2.0.x (any version), 3.0.x through 3.0.5, or 3.5.x through 3.5.3.
-
Confirm Flash Media Server is runningCheck if the FMS service or process is active. On Windows, verify the 'Adobe Flash Media Server' service is running via services.msc. On Linux, run 'ps aux | grep fms' to check for fmserver or fmsmaster processes.Affected if The server is actively running and exposed on the network.
-
Check network exposure of the serverIdentify the listening ports. FMS typically uses ports 1935 (RTMP), 80/443 (HTTP), and 11111 (admin). Use 'netstat -an | grep -E "(1935|80|443|11111)"' or a port scanner to determine if these ports are accessible from untrusted networks.Affected if The server ports are exposed to untrusted or public networks, making it reachable for remote exploitation.
You are affected if Adobe Flash Media Server version 2.0.x, 3.0.x through 3.0.5, or 3.5.x through 3.5.3 is installed and the service is running and network-accessible.
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 Adobe Flash Media Server to version 3.0.6 or later, or 3.5.4 or later, to remediate this vulnerability. Consider network segmentation to limit exposure if immediate upgrade is not feasible.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2219 — 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-2010-2219 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