dbcve.org
ConsolemeApplication · Netflix

CVE-2022-27177

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-01
Fix available
A fix is available. Upgrade to 1.2.2 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
A Python format string issue leading to information disclosure and potentially remote code execution in ConsoleMe for all versions prior to 1.2.2

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

A Python format string vulnerability in ConsoleMe allows attackers to inject format specifiers into user-controlled input, potentially exposing sensitive environment variables or executing arbitrary code through the vulnerable format string processing.

MitigationUpgrade ConsoleMe to version 1.2.2 or later to patch the format string vulnerability.

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
ConsolemeApplication
Affected:< 1.2.2

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.1/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 ConsoleMe installation location
    Locate the ConsoleMe installation directory. Common paths include /opt/consoleme, /usr/local/consoleme, or a virtual environment directory. Check using 'pip show consoleme' or 'pip3 show consoleme' to find the installation path.
    Affected if ConsoleMe is installed in any location but the version cannot be determined or is below 1.2.2
  2. Determine installed ConsoleMe version
    Run 'consoleme --version' or 'pip show consoleme' or 'pip3 show consoleme' to retrieve the installed version number. Alternatively, check the version in setup.py, pyproject.toml, or a VERSION file within the ConsoleMe directory.
    Affected if The installed version is any version earlier than 1.2.2 (e.g., 1.2.1, 1.2.0, 1.1.0, etc.)
  3. Identify format string usage in source code
    Search the ConsoleMe source code for usage of Python format functions with user input. Look for patterns like '.format()', f-strings, or '%' formatting where the arguments may come from request parameters, headers, or user-controlled data. Common search commands: 'grep -r "format"' or 'grep -r "f\'"' in the source directory.
    Affected if Any code path exists where user-supplied input (HTTP parameters, headers, API payloads) is passed directly to Python string formatting methods without sanitization
  4. Check for exposed environment variable access
    Review code that accesses os.environ or similar environment variable sources and trace whether the values are ever used in format string operations. Search using 'grep -r "environ"' and cross-reference with format string usage.
    Affected if Environment variables are accessed and then used in format string operations without validation

A user is affected if ConsoleMe version is below 1.2.2 AND user-controlled input can reach format string processing functions in the application code.

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 1.2.2 or later
Fixed in 1.2.2
Interim mitigation

Upgrade ConsoleMe to version 1.2.2 or later to patch the format string vulnerability.

Recommended fix High confidence

Consoleme version 1.2.2 or later

  1. 1. Identify the currently installed Consoleme version by running: `consoleme --version` or checking your package manager
  2. 2. If running from source, check the version in your installation or Git repository
  3. 3. If your version is below 1.2.2, upgrade Consoleme to version 1.2.2 or later using your package manager (e.g., `pip install --upgrade consoleme` or `pip install consoleme==1.2.2`)
  4. 4. If using a container or cloud deployment, update your container image or deployment configuration to use version 1.2.2
  5. 5. After upgrading, verify the new version is installed: `consoleme --version`
  6. 6. Restart any running Consoleme services to load the patched version
Caveat No breaking changes documented for this security patch release

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

Fix this in Consoleme Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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