Skip to content
Fencer Intel
medium 5.8

CVE-2014-0363 json

The ServerTrustManager component in the Ignite Realtime Smack XMPP API before 4.0.0-rc1 does not verify basicConstraints and nameConstraint…

published 12y ago modified 4mo ago also EUVD-2014-0401

cvss
5.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

The ServerTrustManager component in the Ignite Realtime Smack XMPP API before 4.0.0-rc1 does not verify basicConstraints and nameConstraints in X.509 certificate chains from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate chain.

Patch / fix

  • igniterealtime smack 4.0.0

Is CVE-2014-0363 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-0363 updated cvss 4.3

smack: incorrect X.509 certificate validation

  • Red Hat JBoss BRMS 5 smack smack
    affected: no fix planned “Will not fix”
  • Red Hat JBoss BPMS 6.0
    fixed: vendor fix RHSA-2014:0819
  • Red Hat JBoss BRMS 6.0
    fixed: vendor fix RHSA-2014:0818
  • Red Hat JBoss Fuse 6.2
    fixed: vendor fix RHSA-2015:1176

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.