IBM Support

PM29160: JVM CRASHES WHILE LOADING INVALID CLASS FILE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: A SIGSEGV is reported while loading
invalid/corrupted class file.
.
Stack Trace:
.

Local fix

  • 



Problem summary


    

  • The problem is caused by the classfile parser attempting to
access memory past the end of the classfile due to incorrect
handling of an invalid attribute length field.

    



Problem conclusion


    

  • This defect will be fixed in:

6.0.0 SR10
6.0.0 SR9 FP1
5.0.0 SR13
5.0.0 SR12 FP4
1.4.2 SR13 FP9
.
The JVM has been updated to correctly handle the invalid length
field by throwing a java.lang.ClassFormatError

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PM29160
    • 

  • Reported component name
    JAVA LINUX IA32
    • 

  • Reported component ID
    5648C9804
    • 

  • Reported release
    142
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2010-12-20
    • 

  • Closed date
    2011-02-11
    • 

  • Last modified date
    2011-02-11
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    
IZ89602
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    

  • Fixed component name
    JAVA LINUX IA32
    • 

  • Fixed component ID
    5648C9804
    • 



Applicable component levels


    

  • R142  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.4.2","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            11 February 2011
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback