This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
We need to upgarde axis2 used by SymphonyDE 7.2.0.2 to remidiate our internal security finding related to older version of axis2 (axis2-0.93.jar) used by SymphonyDE 7.2.0.2.
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.
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
.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.
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.