dbcve.org
Jboss A MqApplication · Redhat

CVE-2023-4066

MEDIUM · 5.5 CVSS v3.1 Published 2023-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 flaw was found in Red Hat's AMQ Broker, which stores certain passwords in a secret security-properties-prop-module, defined in ActivemqArtemisSecurity CR; however, they are shown in plaintext in the StatefulSet details yaml of AMQ Broker.

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

Red Hat AMQ Broker stores sensitive passwords in a security-properties-prop-module defined within the ActivemqArtemisSecurity custom resource. These passwords are inadvertently exposed in plaintext within the StatefulSet details YAML, allowing anyone with access to view the YAML to obtain the credentials.

MitigationReplace all plaintext password references in the ActivemqArtemisSecurity CR with Kubernetes Secret object references, then update the AMQ Broker configuration to load passwords from the secrets at runtime.

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
Affected:= 7
Jboss MiddlewareApplication
Affected:= 1
Openshift Container PlatformApplication
Affected:= 4.11= 4.12

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
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 checks

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

  1. Identify ActivemqArtemisSecurity custom resources
    Run 'kubectl get activemqartemissecurity -A' or 'oc get activemqartemissecurity -A' to list all instances of the custom resource in the cluster
    Affected if Any ActivemqArtemisSecurity resource exists in the namespace(s)
  2. Inspect security-properties-prop-module for plaintext passwords
    For each ActivemqArtemisSecurity resource found, run 'kubectl get activemqartemissecurity <name> -n <namespace> -o yaml' and examine the spec.security.securityPropertiesPropModule section for plaintext password values
    Affected if The securityPropertiesPropModule section contains plaintext password strings rather than secret references
  3. Check StatefulSet YAML for exposed credentials
    Run 'kubectl get statefulset -n <namespace> -o yaml' for each namespace containing AMQ Broker, and search within the spec.template.spec.containers section for any plaintext password strings that match those in the ActivemqArtemisSecurity resource
    Affected if The StatefulSet YAML output contains plaintext password strings in environment variables or configuration
  4. Verify password storage method in CR spec
    Examine the full YAML output of ActivemqArtemisSecurity custom resources and look specifically at any property 'password' or 'secretName' fields under the security configuration sections
    Affected if Passwords are stored directly in the CR YAML under plain field names rather than referencing Kubernetes Secret objects
  5. Review access to StatefulSet YAML
    Check cluster RBAC permissions to determine which users or service accounts can read StatefulSet resources via 'kubectl auth can-i get statefulsets --as=<user>'
    Affected if Users other than cluster administrators can view StatefulSet YAML in namespaces running AMQ Broker

A user is affected if their ActivemqArtemisSecurity custom resources contain plaintext passwords in security-properties-prop-module that are then visible in the corresponding StatefulSet YAML configuration.

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

Replace all plaintext password references in the ActivemqArtemisSecurity CR with Kubernetes Secret object references, then update the AMQ Broker configuration to load passwords from the secrets at runtime.

Fix this in Jboss A Mq 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 help mitigating

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-4066 — 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-4066 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