Security framework of XStream not initialized, XStream is probably vulnerable

后端 未结 3 728
耶瑟儿~
耶瑟儿~ 2021-01-03 18:30

Security framework of XStream not initialized, XStream is probably vulnerable

I keep getting this console error in red while using XStream (1.4.10)

3条回答
  •  隐瞒了意图╮
    2021-01-03 19:03

    When dealing with security issues, I wouldn't take it lightly. Firstly one would understand the severity of the issue, here a good write up or another one.

    Then find out how people recommend the solution. The good place to start is from xstream website itself. There is an example which you can use as a starting point on xstream security page.

    This would be my set up which basically allows most of your code.

    XStream xstream = new XStream();
    // clear out existing permissions and set own ones
    xstream.addPermission(NoTypePermission.NONE);
    // allow some basics
    xstream.addPermission(NullPermission.NULL);
    xstream.addPermission(PrimitiveTypePermission.PRIMITIVES);
    xstream.allowTypeHierarchy(Collection.class);
    // allow any type from the same package
    xstream.allowTypesByWildcard(new String[] {
        "com.your.package.**"
    });
    

    However, after diving more into their source code, this is my take:

    XStream.setupDefaultSecurity(this); // to be removed after 1.5
    xstream.allowTypesByWildcard(new String[] {
        "com.your.package.**"
    });
    

    So essentially, you will need just one line once upgrading to 1.5.

    Please note that you may need more wild cards to suit your application deserialization scenarios. This is not a one-size-fit-all answer but rather a good starting point IMHO.

提交回复
热议问题