dbcve.org
MegamekApplication

CVE-2018-1000824

CRITICAL · 9.8 CVSS v3.0 Published 2018-12-20
Fix available
A fix is available. Upgrade to 0.45.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
MegaMek version < v0.45.1 contains a Other/Unknown vulnerability in Object Stream Connection that can result in Disclosure of confidential data, denial of service, SSRF, remote code execution.

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 confidence

MegaMek versions prior to v0.45.1 contain an insecure deserialization vulnerability in the Object Stream Connection component. This Java deserialization flaw allows attackers to manipulate serialized object streams, potentially achieving remote code execution, SSRF, data disclosure, or denial of service.

MitigationUpgrade to MegaMek v0.45.1 or later. If immediate upgrade is not feasible, restrict network exposure to the vulnerable component and implement strict authentication for object stream connections.

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
MegamekApplication
Affected:< 0.45.1

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MegaMek installation and version
    Locate the MegaMek installation directory. Check for version information in the program folder, such as a version.txt file, about dialog, or the megamek.jar manifest. Alternatively, run MegaMek with --version or check startup logs for version output.
    Affected if The installed version is lower than 0.45.1
  2. Locate Java deserialization configuration
    Search the MegaMek configuration directory for files containing 'ObjectStream' or 'serial' related settings. Check config.xml, megamek.xml, or any .properties files for serialization-related parameters.
    Affected if Object Stream Connection feature is enabled in configuration files
  3. Identify network listeners and ports
    Review MegaMek network configuration or server settings for ports that accept object stream connections. Check for server-mode configurations that listen for incoming connections.
    Affected if MegaMek is configured to accept network connections on ports using object serialization
  4. Check for exposed network services
    Scan the host running MegaMek for listening ports, particularly any custom ports used by MegaMek for multiplayer or server functionality. Review firewall rules or network exposure settings.
    Affected if MegaMek network services are accessible from untrusted networks

You are affected if MegaMek version is below 0.45.1 AND the Object Stream Connection component is enabled and accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 0.45.1 or later
Fixed in 0.45.1
Interim mitigation

Upgrade to MegaMek v0.45.1 or later. If immediate upgrade is not feasible, restrict network exposure to the vulnerable component and implement strict authentication for object stream connections.

Recommended fix High confidence

MegaMek 0.45.1 or later

  1. 1. Identify the current MegaMek version installed by checking the application or its about/info section
  2. 2. Obtain MegaMek version 0.45.1 or later from the official distribution source (github.com/megamek/megamek/releases)
  3. 3. Create a backup of existing MegaMek installation directory and any saved games/configuration files
  4. 4. Install the upgraded version (0.45.1 or later) by extracting or running the installer
  5. 5. Restore backed-up configuration and saved game files to the new installation
  6. 6. Verify the new version by checking the application version information
Caveat Minor compatibility changes may exist between versions; test any custom configurations or saved games after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Megamek Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000824 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000824 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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