IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Spectrum Symphony
Components Version
Created by Guest
Created on Apr 23, 2021

SymphonyDE doesn't work with axis2 1.6.2 version of Axis2

We need to upgarde axis2 used by SymphonyDE to remidiate our internal security finding related to older version of axis2 (axis2-0.93.jar) used by SymphonyDE

I tested our code with publicly available version of Axis2 ( I tried 0.9, 1.0, 1.41 and 1.6.2) and code only works with axis2 that comes with IBM symphoney installation.

If we use ego.jar and axis2-0.93.jar from below symphony instllation directory then our code works ( /auto/opt_symphonyDE/DE7.2.0.2/ego_sdk/3.6/linux-x86_64/lib). If we use any publicly available version of Axis2 then code doesn't work.

  • Guest
    Aug 5, 2021

    .Mark this RFE request status as the reported issues had been analyzed and confirmed Symphony is not vulnerable to the issues. Ashwini please feel free to open new ticket or request if there are any other issues.

  • Guest
    May 27, 2021

    Analysis of the CVEs reported regarding Asix2 0.93:

    - CVE-2010-1632:
    Problem: Axis2 (1.5.2 and older version) does not properly reject DTDs in SOAP messages, which allows remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service (CPU and memory consumption) via a crafted DTD.
    Symphony analysis: After EGO SDK (i.e. ego.jar)is created, there is no way to assemble a SOAP messages including a DTD into EGO SDK. Symphony WSDL Server doesn't use Axis2.
    Conclusion: This vulnerability does not apply to Symphony.

    - CVE-2012-5785:
    Problem: Axis2 (1.6.2 and older version) does not verify that the server host name matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
    Symphony analysis: Symphony uses Axis2 only in EGO WSDL client. This CVE impacts the server side only. And Symphony WSDL Server does not use Axis 2, instead the server is implemented by language C based on OpenSSL.
    Conclusion: This vulnerability does not apply to Symphony.