Jboss A MqApplication · Redhat
CVE-2023-4065
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 · uneditedA flaw was found in Red Hat AMQ Broker Operator, where it displayed a password defined in ActiveMQArtemisAddress CR, shown in plain text in the Operator Log. This flaw allows an authenticated local attacker to access information outside of their permissions.
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 confidenceRed Hat AMQ Broker Operator logs passwords defined in ActiveMQArtemisAddress custom resources in plain text, allowing authenticated local attackers with log access to retrieve sensitive credentials.
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
Jboss A MqApplication
= 7
Jboss MiddlewareApplication
= 1
Openshift Container PlatformApplication
= 4.11= 4.12CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if AMQ Broker Operator is installedRun 'oc get csv -n operators | grep amq' or 'kubectl get csv -n operators | grep amq' to list installed operator subscriptionAffected if No AMQ Broker Operator is installed, the environment is not affected by this CVE
-
Check for ActiveMQArtemisAddress custom resourcesRun 'oc get artemisaddress -A' or 'kubectl get artemisaddress --all-namespaces' to list custom resources in the clusterAffected if No ActiveMQArtemisAddress resources exist, passwords cannot be exposed through this vector
-
Inspect operator logs for plain text passwordsRun 'oc logs -n operators deployment/<amq-broker-operator-pod>' or 'kubectl logs -n operators deployment/<amq-broker-operator-pod>' and search for patterns matching 'password' or credential field valuesAffected if Logs contain plain text password strings from ActiveMQArtemisAddress resources, the environment is vulnerable
-
Verify log access controlsReview cluster role bindings and check which users have access to operator namespace logs using 'oc auth can-i get logs --as=<user>' or audit log access policiesAffected if Unauthenticated or low-privilege users can access operator logs, the plain text exposure is exploitable
The environment is affected if the AMQ Broker Operator is installed, ActiveMQArtemisAddress resources with passwords exist, and those logs containing plain text credentials are accessible to attackers.
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.
From vendor dataImplement log redaction/scrubbing for sensitive fields, restrict log access, and apply any available vendor patches.
Fix this in Jboss A Mq
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-4065 — 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-2023-4065 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