2017-03-13 73 views
0

我在使用加密的生产环境中遇到问题。生产环境中的加密异常

下面的代码是问题的根源:

public static void standardExceptionHandling(Exception exc, Logger alog) { 
    StringWriter sw = new StringWriter(); 
    PrintWriter pw = new PrintWriter(sw); 
    exc.printStackTrace(pw); 
    alog.info(sw.toString()); /* Line 292 */ 
} 

/** 
* Method that takes a key/value set, converts it into a standard web parameter string 
* and then encrypts the string. 
* 
* @param values the key value set 
* @return the encrypted string 
* 
*/ 
public static String encrypt(Map<String, String> values) { 
    StringBuilder unencrypted = new StringBuilder(); 
    boolean first = true; 
    for (Map.Entry<String, String> value : values.entrySet()) { 
     if (first) { 
      first = false; 
     } else { 
      unencrypted.append("&"); 
     } 
     unencrypted.append(value.getKey()) 
       .append("=") 
       .append(value.getValue()); 
    } 

    try { 
     Cipher cipher = Cipher.getInstance("AES"); 
     Key aesKey = new SecretKeySpec(AES_KEY.getBytes(), "AES"); 
     cipher.init(Cipher.ENCRYPT_MODE, aesKey); 
     byte[] encrypted = cipher.doFinal(unencrypted.toString().getBytes("UTF8")); 

     String enc = new sun.misc.BASE64Encoder().encode(encrypted); 
     return enc; 
    } catch (Exception e) { 
     standardExceptionHandling(e, log); 
     return ""; 
    } 
} 

/** 
* Method that takes an encrypted string containing a standard web parameter string 
* and converts it to a key/value set 
* 
* @param encrypted the encrypted string 
* @return the key value set 
*/ 
public static Map<String, String> decrypt(String encrypted) { 
    String decrypted = ""; 
    try { 
     Cipher cipher = Cipher.getInstance("AES"); 
     Key aesKey = new SecretKeySpec(AES_KEY.getBytes(), "AES"); 
     cipher.init(Cipher.DECRYPT_MODE, aesKey); 
     byte[] dec = new sun.misc.BASE64Decoder().decodeBuffer(encrypted); 
     decrypted = new String(cipher.doFinal(dec), "UTF8"); 
    } catch (Exception e) { 
     standardExceptionHandling(e, log); 
    } 

    Map<String, String> values = new HashMap<String, String>(); 
    for (String pair : decrypted.split("&")) { 
     String[] split_pair = pair.split("="); 
     String key, value; 
     if (split_pair.length == 1) { 
      key = split_pair[0]; 
      value = ""; 
     } else if (split_pair.length == 2) { 
      key = split_pair[0]; 
      value = split_pair[1]; 
     } else if (split_pair.length > 2) { 
      log.debug("Error when decrypting string, parameter found with more than 2 parts (" + pair + ")"); 
      continue; 
     } else { 
      // We should never reach this, as it is impossible to split a string into a 0 length array. 
      log.debug("The impossible happened, we split a String into a 0 length array (" + pair + ")"); 
      continue; 
     } 
     // This is only reach when key and value have been initialised thank to the continue statements when we hit 
     // an error state. 
     values.put(key, value); 
    } 
    return values; 
} 

没有例外加密文本时抛出。 加密后,它是通过一个URL通过servlet传回

http://URL/servlet?hash=TVgYDScPqQ3eaJfEBmwuSCZUN0GCEshOBZ9H0YKH%2BS2b96BYdLRPBa6Dl8Z0mMmpPM1r2uxdv0sq%0A5BNbWTMcww%3D%3D

在我们的生产服务器,我们得到以下异常:

INFO 10/mar/2017 06:02:37 [http-nio-80-exec-104] (HelperMethods.java:292) - javax.crypto.IllegalBlockSizeException: Input length must be multiple of 16 when decrypting with padded cipher 
at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:913) 
at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:824) 
at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:436) 
at javax.crypto.Cipher.doFinal(Cipher.java:2165) 
at com.gg.gomoenterprise.utils.HelperMethods.decrypt(HelperMethods.java:349) 
at com.gg.gomomessenger.servlets.EmailServlet.doPost(EmailServlet.java:60) 
at com.gg.gomomessenger.servlets.EmailServlet.doGet(EmailServlet.java:46) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) 
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) 
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) 
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) 
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) 
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) 
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) 
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518) 
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091) 
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:673) 
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1526) 
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1482) 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) 
at java.lang.Thread.run(Thread.java:745) 
DEBUG 10/mar/2017 06:02:37 [http-nio-80-exec-104] (EmailServlet.java:88) - com.gg.gomomessenger.commons.exceptions.EmailSeverletException: <h1>We do not see your email address in this program. You may have already unsubscribed or be subscribed with a different email address. If you need assistance, email [email protected]</h1> 
at com.gg.gomomessenger.commons.exceptions.EmailSeverletException.dataMisingException(EmailSeverletException.java:39) 
at com.gg.gomomessenger.servlets.EmailOptInServlet.handleOpt(EmailOptInServlet.java:91) 
at com.gg.gomomessenger.servlets.EmailServlet.doPost(EmailServlet.java:82) 
at com.gg.gomomessenger.servlets.EmailServlet.doGet(EmailServlet.java:46) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) 
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) 
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) 
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) 
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) 
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) 
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) 
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518) 
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091) 
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:673) 
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1526) 
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1482) 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) 
at java.lang.Thread.run(Thread.java:745) 

这仅发生在生产,而不是本地,dev或staging。 所有的服务器都运行Tomcat 8.0.26

本地JRE Java版本 “1.8.0_121” 的Java(TM)SE运行时环境(建1.8.0_121-B13) 的HotSpot的Java(TM)64位服务器VM(建立25.121-B13,混合模式)

分期JRE Java版本 “1.8.0_66” 的Java(TM)SE运行时环境(建立1.8.0_66-B17) 的HotSpot的Java(TM)64位服务器VM(版本25.66-b17,混合模式)

Stagin JRE Java版本 “1.8.0_66” 的Java(TM)SE运行时环境(建立1.8.0_66-B17) 爪哇热点(TM)64位服务器VM(建立25.66-B17,混合模式)

生产JRE Java版本 “1.8.0_60” 的Java(TM)SE运行时环境(建立1.8.0_60-B27) 爪哇热点(TM)64位服务器VM(建立25.60-B23,混合模式)

这可能是一个代码问题?

+0

在调试什么是数据长度(dec的长度)时,它必须是块大小的倍数,AES的16字节?错误消息:“当使用填充密码解密时,输入长度必须是16的倍数”说明一切。 – zaph

+1

您在生产环境中使用该代码?它使用ECB模式......你应该修复这个问题。 –

+0

@LukePark,不是很有帮助....你能告诉我什么使用。而不是仅仅说“修复” 此外,这并不意味着是一个主要的加密算法,它只是简单地隐藏用户的4个参数。 如果我们没有加密,我们会传递4个参数,他们都需要匹配(所有不同但链接)。如果他们不正确链接,页面将不会加载! –

回答

2

我注意到例如:

TVgYDScPqQ3eaJfEBmwuSCZUN0GCEshOBZ9H0YKH%2BS2b96BYdLRPBa6Dl8Z0mMmpPM1r2uxdv0sq%0A5BNbWTMcww%3D%3D

是URL编码,并包含一个换行字符(%0A)。 Base64需要删除URL编码。

此外,Base64编码不应该添加换行字符,应该有一个选项。无论如何,他们都需要在Base64解码上剥离。

正确解码它是十六进制:

4D58180D270FA90DDE6897C4066C2E48265437418212C84E059F47D18287F92D9BF7A05874B44F05AE8397C67498C9A93CCD6BDAEC5DBF4B2AE4135B59331CC3

+0

采取的措施...我错过了URLDecode,即使加密做URLEncode,谢谢! 但是,您是否有任何解释说明为什么它在其他环境中使用完全相同的设置。 –

+1

好运。根据加密的数据,Base64编码中可能不会有“+”和“/”,并且根据长度,UIRL编码没有尾随“=”字符。换行符0x0A通常由Base64解码功能删除。 – zaph

+0

虽然,我真的很喜欢你的答案,并且肯定会把它看作是一个问题....我真的很惊讶这只是运气,它只发生在PROD中。 但是,在另一方面,我们没有测试太多,....我们做了一个紧急修复程序,回去删除加密。也许一些散列wouyd已经在生产中工作。 –

0

正如@zaph指出的那样,有可能解析所述密文中的问题,这会导致不同长度的密文从的倍数块大小(16 bytes)。在正确编码和解码密文后,您应该能够验证密文长度是n * 16字节。

此外,您获得Cipher类的实例Cipher.getInstance("AES");的实例并不理想。默认情况下,Java中的AESAES/ECB/PKCS5Padding(但这也可能因供应商而异)。 ECB是一个不推荐/不推荐/破碎的block cipher mode。除了不知不觉地选择了一种糟糕的操作模式之外,这里的含糊不清是没有必要的。评估可用模式并明确选择合适的模式(可能的GCM或可能的CBCCTR与强大的HMAC功能一起使用)。

对于每个消息加密,您还应该使用唯一且不可预测的初始化向量(IV)。

+1

请显示ECB模式在哪里是不推荐/破碎的分组密码模式。 – zaph

+0

@ zaph:欧洲央行不安全是常识:http://crypto.stackexchange.com/questions/20941/why-shouldnt-i-use-ecb-encryption – Robert

+0

也许这些条款很强大,但取决于您的威胁模型,我站在他们旁边。一个明显的例子是[“企鹅形象”](https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation#Electronic_Codebook_.28ECB.29),但有[许多](http://crypto.stackexchange.com/ a/20946/12569)[其他](http://crypto.stackexchange.com/a/968/12569)[示例](https://security.stackexchange.com/a/62084/16485)'ECB'模式对现代密码分析不安全。 – Andy