#2669 Potential null pointer exception in parseMESSAGE

Code_Cleanup
closed-fixed
jsr48-client
5
2013-12-13
2013-09-24
No

CIMXMLParserImpl.parseMESSAGE() assumes all MESSAGE elements come with a valid ID attribute and use Attr.getNodeValue() without making sure Attr isn't null. Also, the PROTOCOLVERSION isn't verified at all.

1 Attachments

Discussion

  • Dave Blaschke

    Dave Blaschke - 2013-09-24

    Patch sent for community review. During a 2 week period any exploiter may comment on the patch, request changes or turn it down completely (with good reason). For the time being the patch is part of the "Experimental" branch in CVS.

     
  • Dave Blaschke

    Dave Blaschke - 2013-09-24
    • status: open --> open-fixed
     
  • Dave Blaschke

    Dave Blaschke - 2013-10-09
    • status: open-fixed --> pending-fixed
     
  • Dave Blaschke

    Dave Blaschke - 2013-10-09

    The community review is completed and we received no substantial criticism. Therefore the patch has been approved and merged into the "HEAD" branch. The next release will pick it up.

     
  • Dave Blaschke

    Dave Blaschke - 2013-12-13

    The patch was picked up by release 2.2.5 and will be closed.

     
  • Dave Blaschke

    Dave Blaschke - 2013-12-13
    • status: pending-fixed --> closed-fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks