dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-53304

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
An issue in LRQA Nettitude PoshC2 after commit 09ee2cf allows unauthenticated attackers to connect to the C2 server and execute arbitrary commands via posing as an infected machine.

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 confidence

An authentication bypass vulnerability in LRQA Nettitude PoshC2 after commit 09ee2cf allows unauthenticated remote attackers to connect to the C2 server by impersonating infected machines, enabling execution of arbitrary commands on the compromised C2 infrastructure.

MitigationRestrict network access to the C2 server to trusted sources immediately; update PoshC2 to the latest version once a patch is released or revert to a version before commit 09ee2cf.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

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

  1. Locate the PoshC2 installation directory
    Identify the directory where PoshC2 is installed (commonly /opt/PoshC2, /root/PoshC2, or a custom path). If you deployed PoshC2 yourself, use the directory where you cloned or installed it.
    Affected if PoshC2 is installed and the directory exists on the system
  2. Check the git commit hash
    Navigate to the PoshC2 directory and run 'git log --oneline -1' to obtain the current commit hash. Compare this hash to commit 09ee2cf.
    Affected if The current commit hash is later than (comes after) 09ee2cf in the git history - meaning the commit includes changes after the fix point
  3. Verify network exposure of the C2 server
    Identify the network interface and port the PoshC2 server listens on (check config files or running processes). Determine if this is accessible from untrusted networks or the public internet.
    Affected if The C2 server is reachable from untrusted/external networks without firewall restrictions

If PoshC2 is installed and the git commit is after 09ee2cf with the C2 server exposed to untrusted networks, the environment is vulnerable to unauthenticated C2 impersonation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the C2 server to trusted sources immediately; update PoshC2 to the latest version once a patch is released or revert to a version before commit 09ee2cf.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53304 — 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-2024-53304 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