# HTTP Request Smuggling issue in neo4j java driver

**URL:** <https://community.neo4j.com/t/http-request-smuggling-issue-in-neo4j-java-driver/15580>\
**Category:** Java\
**Created:** [March 10, 2020, 10:36am UTC](https://community.neo4j.com/t/http-request-smuggling-issue-in-neo4j-java-driver/15580 "2020-03-10T10:36:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![a.seenivasan1](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/a.seenivasan1/32/7459_2.png) [@a.seenivasan1](https://community.neo4j.com/u/a.seenivasan1)\
**Post date:** [March 10, 2020, 10:36am UTC](https://community.neo4j.com/t/http-request-smuggling-issue-in-neo4j-java-driver/15580/1 "2020-03-10T10:36:51Z")

</div>

I found the below security vulnerabilities in neo4j java driver . we are using   
  
org.neo4j.driver  
neo4j-java-driver  
1.7.5

| CVE-2020-7238 | Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869. |
| --- | --- |
| CVE-2019-20444 | HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an "invalid fold." |
| CVE-2019-16869 | Netty before 4.1.42.Final mishandles whitespace before the colon in HTTP headers (such as a "Transfer-Encoding : chunked" line), which leads to HTTP request smuggling. |

neo4j-java-driver-1.7.5.jar\META-INF/maven/io.netty/netty-transport/pom.xml (pkg:maven/io.netty/netty-transport@4.1.22.Final, cpe:2.3:a:netty:netty:4.1.22:_:_:_:_:_:_:\*) : CVE-2019-16869, CVE-2019-20444, CVE-2019-20445