CVE-2024-9858
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 · uneditedThere exists an insecure default user permission in Google Cloud Migrate to containers from version 1.1.0 to 1.2.2 Windows installs. A local "m2cuser" was greated with administrator privileges. This posed a security risk if the "analyze" or "generate" commands were interrupted or skipping the action to delete the local user “m2cuser”. We recommend upgrading to 1.2.3 or beyond
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 confidenceGoogle Cloud Migrate to containers (Windows versions 1.1.0-1.2.2) creates a local user account named 'm2cuser' with administrator privileges during its 'analyze' or 'generate' operations. If these commands are interrupted or skip the cleanup action, the high-privilege local user persists on the system, creating a local privilege escalation and persistence vector.
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.1.0, < 1.2.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Google Migrate To Containers is installedOpen Programs and Features (appwiz.cpl) or check C:\Program Files\Google\Migrate To Containers for the executable and version. Alternatively, run: dir 'C:\Program Files\Google\Migrate To Containers' /bAffected if The product is installed and version is >= 1.1.0 and < 1.2.3
-
Verify m2cuser account exists on the systemOpen Computer Management > Local Users and Groups > Users, or run: net user m2cuserAffected if The m2cuser account exists on the system
-
Check if m2cuser has administrator privilegesOpen Computer Management > Local Users and Groups > Groups > Administrators, or run: net localgroup Administrators | findstr m2cuserAffected if The m2cuser account is listed as a member of the Administrators group
-
Review analyze or generate command execution historyCheck event logs, scheduled tasks, or migration logs for interrupted or failed 'm2c analyze' or 'm2c generate' operations that may have skipped cleanupAffected if There are records of analyze or generate commands that were interrupted or did not complete cleanup
You are affected if Google Migrate To Containers version 1.1.0 to 1.2.2 is installed AND the m2cuser account exists on the system with administrator privileges.
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.
dbcve · scoped1.2.3
Upgrade Google Cloud Migrate to containers to version 1.2.3 or later, which addresses the insecure default user permission by properly cleaning up the m2cuser account.
1.2.3 or later
- Upgrade Google Cloud Migrate to Containers to version 1.2.3 or later to remediate the insecure default user permission vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing6.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,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9858 — 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-2024-9858 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