このコンテンツは選択した言語では利用できません。
Chapter 7. Resolved Issues
7.1. Resolved Issues
- JDG-1364 - IndexedField annotation in proto file causes java.lang.NumberFormatException
When using
@IndexedField(index=true)
, a Java exception could be generated.This issue is resolved as of JBoss Data Grid 7.1.2.
- JDG-1390 - ProtoSchemaGenerator fails in Karaf: CNFE: org.infinispan.protostream.RawProtobufMarshaller
JBoss Data Grid previously included Protostream 4.1.1, which would not work with Apache Karaf. Protostream has been upgraded to 4.1.3.
This issue is resolved as of JBoss Data Grid 7.1.2.
- JDG-1396 - CVE-2014-9970 jasypt: Vulnerable to timing attack against the password hash comparison [jdg-7.1.0]
A vulnerability was found in Jasypt that would allow an attacker to perform a timing attack on password hash comparison. Jasypt has been removed.
This issue is resolved as of JBoss Data Grid 7.1.2.
- JDG-1409 - CVE-2017-7525 jackson-databind: Deserialization vulnerability via readValue method of ObjectMapper [jdg-7.1.0]
A deserialization flaw in jackson-databind was found allowing code execution when given maliocusly crafted input to readValue method of ObjectMapper. jackson-databind has been removed.
This issue is resolved as of JBoss Data Grid 7.1.2.
- JDG-1410 - CVE-2017-15089 infinispan-core: infinispan: Unsafe deserialization of malicious object injected into data cache [jdg-7.1.0]
A vulnerability in Infinispan was found which allowed malicious users to inject malicious serialized objects into the server’s data cache and potentially execute arbitrary code on another user’s computer when the malicious data was fetched using the hot rod protocol.
This issue is resolved as of JBoss Data Grid 7.1.2.
- JDG-1432 - RESTEASY002115: Attempting to register unassignable contract for org.infinispan.rest.logging.RestAccessLoggingHandler warning is generated on startup
When the server was started the above warning message could be generated. This was caused by RESTEasy performing a class check while registering resources when classes didn’t match.
This issue is resolved as of JBoss Data Grid 7.1.2.