dbcve.org
PowerjobApplication

CVE-2023-36106

HIGH · 7.5 CVSS v3.1 Published 2023-08-17
Fix available
A fix is available. Upgrade to after 4.3.2 or later.
See remediation →
84/100
Remediation priority · High
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 incorrect access control vulnerability in powerjob 4.3.2 and earlier allows remote attackers to obtain sensitive information via the interface for querying via appId parameter to /container/list.

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

The powerjob application has an incorrect access control vulnerability in the /container/list endpoint. This endpoint accepts an appId parameter and returns sensitive information, but lacks proper authentication or authorization checks, allowing unauthenticated remote attackers to query container information by manipulating the appId parameter.

MitigationImplement proper authentication and authorization checks on the /container/list endpoint to ensure only authenticated users with appropriate permissions can access container information. Validate that the requesting user has rights to access the specific appId being requested.

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
PowerjobApplication
Affected:<= 4.3.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify Powerjob installation
    Locate the Powerjob service in your environment by checking running processes, deployed applications, or service configurations. Look for process names or web applications named 'powerjob'.
    Affected if Powerjob is installed and running in your environment
  2. Determine Powerjob version
    Check the deployed Powerjob version by examining the JAR/WAR file name, build metadata, or accessing the application's main endpoint (such as /health or /about) if available. Compare against the affected version range.
    Affected if The installed version is 4.3.2 or lower
  3. Verify endpoint accessibility
    Attempt to access the /container/list endpoint from an unauthenticated context (no session cookie, token, or credentials). Use a tool like curl: curl -s http://TARGET_HOST/container/list
    Affected if The endpoint responds with HTTP 200 and returns container information without requiring authentication
  4. Confirm sensitive data exposure
    Append the appId parameter to the request: curl -s 'http://TARGET_HOST/container/list?appId=test' and examine the response. Check if the response contains sensitive container configuration details, credentials, or internal information.
    Affected if The endpoint returns sensitive container data (such as appName, appConfig, or other internal details) without any authentication token

If Powerjob version 4.3.2 or lower is running AND the /container/list endpoint is accessible without authentication AND returns container information, the environment is affected by CVE-2023-36106.

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 a release after 4.3.2
Interim mitigation

Implement proper authentication and authorization checks on the /container/list endpoint to ensure only authenticated users with appropriate permissions can access container information. Validate that the requesting user has rights to access the specific appId being requested.

Recommended fix Moderate confidence

Powerjob 4.3.3 or later

  1. 1. Identify all Powerjob deployments running version 4.3.2 or earlier
  2. 2. Upgrade Powerjob to the latest stable release (version 4.3.3 or later) which contains the access control fix
  3. 3. Verify the upgrade was successful by checking the Powerjob version in the admin console
  4. 4. Test the /container/list endpoint to confirm proper access control is enforced
  5. 5. Review application logs for any unauthorized access attempts that may have occurred prior to patching
Caveat Review release notes for any breaking changes between 4.3.2 and the target upgrade version before deploying to production

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

Fix this in Powerjob Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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