dbcve.org
Openpages With WatsonApplication · Ibm

CVE-2024-49782

HIGH · 8.2 CVSS v3.1 Published 2025-02-20
Fix available
A fix is available. Upgrade to 8.3.0.3 / 9.0.0.5 or later.
See remediation →
91/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
IBM OpenPages with Watson 8.3 and 9.0  could allow a remote attacker to spoof mail server identity when using SSL/TLS security. An attacker could exploit this vulnerability to gain access to sensitive information disclosed through email notifications generated by OpenPages or disrupt notification delivery.

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 confidence

IBM OpenPages fails to properly validate SSL/TLS certificates when connecting to mail servers, allowing a remote attacker to spoof the mail server identity and perform a man-in-the-middle attack. This enables interception of sensitive information in email notifications or disruption of notification delivery.

MitigationImplement proper SSL/TLS certificate validation including hostname verification and certificate chain trust validation in the mail server configuration, or apply vendor patches if available.

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
Openpages With WatsonApplication
Affected:>= 8.3, < 8.3.0.3>= 9.0, < 9.0.0.5

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L

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 installed IBM OpenPages version
    Locate the OpenPages installation directory and check the version manifest, about page, or version file. Common locations include the installation root or a version info file within the OpenPages application directory.
    Affected if The installed version is 8.3.x before 8.3.0.3, or 9.0.x before 9.0.0.5.
  2. Verify mail server configuration exists
    Check the OpenPages configuration files for mail server settings. Look for SMTP or email-related configuration sections in the application configuration directory.
    Affected if A mail server connection is configured or enabled in the OpenPages environment.
  3. Inspect SSL/TLS validation settings for mail connections
    Review the mail server connection configuration for any settings related to certificate validation, trust store configuration, or SSL/TLS verification. Check whether certificate validation is disabled or improperly configured.
    Affected if SSL/TLS certificate validation is disabled, set to skip verification, or not properly configured for mail server connections.

The environment is affected if OpenPages version is 8.3.0.0 through 8.3.0.2 or 9.0.0.0 through 9.0.0.4 AND mail server connectivity is configured with improper SSL/TLS certificate validation.

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 8.3.0.3 / 9.0.0.5 or later
Fixed in 8.3.0.39.0.0.5
Interim mitigation

Implement proper SSL/TLS certificate validation including hostname verification and certificate chain trust validation in the mail server configuration, or apply vendor patches if available.

Recommended fix High confidence

8.3.0.3 (for 8.3.x) or 9.0.0.5 (for 9.0.x)

  1. 1. Back up your current IBM OpenPages with Watson installation and database before upgrading.
  2. 2. Download the fixed version (8.3.0.3 for 8.x or 9.0.0.5 for 9.x) from IBM Fix Central or through your IBM support channel.
  3. 3. Review IBM OpenPages upgrade documentation for your specific version path.
  4. 4. Apply the upgrade following IBM's standard upgrade procedures for your deployment type.
  5. 5. After upgrade, verify that SSL/TLS certificate validation is properly configured for mail server connections in the OpenPages administration settings.
  6. 6. Test email notification functionality to confirm the fix is working correctly.
Caveat Minor patch upgrade - minimal expected breaking changes, but test in non-production environment first

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

Fix this in Openpages With Watson Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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