dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-51123

HIGH · 7.5 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 issue in Zertificon Z1 SecureMail Z1 SecureMail Gateway 4.44.2-7240-debian12 allows a remote attacker to obtain sensitive information via the /compose-pdf.xhtml?convid=[id] component.

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 Z1 SecureMail Gateway web application has an information disclosure vulnerability in the /compose-pdf.xhtml endpoint. By manipulating the convid (conversation ID) parameter, an unauthenticated remote attacker can access sensitive information that should require proper authorization. This appears to be an Insecure Direct Object Reference (IDOR) or broken access control issue allowing unauthorized access to PDF composition data.

MitigationImplement proper authentication and authorization checks on the /compose-pdf.xhtml endpoint to ensure users can only access conversation data they are explicitly authorized to view. Consider adding session validation and role-based access control (RBAC) for all sensitive endpoints.

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
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 if Z1 SecureMail Gateway is deployed
    Check your environment for the Z1 SecureMail Gateway web application. Look for running services on common ports (typically 443, 8443) or check installed software listings for Z1 SecureMail Gateway.
    Affected if Z1 SecureMail Gateway is installed and running in your environment.
  2. Determine the installed version
    Locate the version information for your Z1 SecureMail Gateway installation. This may be available in the web interface footer, admin panel, or installation documentation. Compare your version against any release notes or patch information related to CVE-2024-51123.
    Affected if Your version is older than the patched version for this CVE.
  3. Verify /compose-pdf.xhtml endpoint accessibility
    Attempt to access the /compose-pdf.xhtml endpoint on your Z1 SecureMail Gateway server (e.g., https://yourserver/compose-pdf.xhtml). Observe whether the endpoint responds with any content or redirects.
    Affected if The endpoint is accessible and returns a response without requiring authentication.
  4. Test unauthenticated access to conversation data
    Send a request to /compose-pdf.xhtml with a convid parameter value (e.g., convid=1, convid=2) without providing any authentication credentials. Check if the response contains sensitive PDF composition data or conversation information.
    Affected if You can access conversation data without valid authentication credentials.
  5. Confirm IDOR vulnerability via parameter manipulation
    If authenticated, access your own conversation via the /compose-pdf.xhtml endpoint and note the convid value. Then log out or use an incognito session and attempt to access a different convid value. Determine if you can view conversations belonging to other users or conversations you are not authorized to access.
    Affected if Manipulating the convid parameter allows access to conversation data that should require proper authorization.

Your environment is affected if Z1 SecureMail Gateway is running with the vulnerable endpoint accessible and the convid parameter can be manipulated to access conversation data without proper authentication or authorization.

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

Implement proper authentication and authorization checks on the /compose-pdf.xhtml endpoint to ensure users can only access conversation data they are explicitly authorized to view. Consider adding session validation and role-based access control (RBAC) for all sensitive endpoints.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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