Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CLSA-2026-1777446601 — libservlet3.0-java (CVE-2020-13935)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Fix CVE(s): CVE-2020-13935

  • SECURITY UPDATE: denial of service via crafted WebSocket frame with

a 64-bit payload length whose most significant bit is set. The

extended payload length read in WsFrameBase.processRemainingHeader()

was assembled into a Java long without validation. With bit 63 set

the value became negative, which the consumer then used as a loop

bound, causing an infinite loop and exhausting CPU on the server

thread. Affects Apache Tomcat 7.0.0 to 7.0.104, 8.5.0 to 8.5.56,

9.0.0.M1 to 9.0.36, and 10.0.0-M1 to 10.0.0-M6.

  • debian/patches/CVE-2020-13935.patch: validate the 64-bit payload

length in processRemainingHeader() and reject frames with a

negative value by throwing a WsIOException carrying a

PROTOCOL_ERROR close reason; add the wsFrame.payloadMsbInvalid

message to LocalStrings.properties. Also fold the companion fix

4c04982870 to apply the same validation to the legacy

org/apache/catalina/websocket/WsFrame parser (still packaged in

catalina.jar via WebSocketServlet), and the regression follow-up

34d19fbe24 in WsFrameBase.byteArrayToLong() (0xFF -> 0xFFL) that

prevents silent corruption of payload lengths >= 4 bytes from

int-shift promotion. Additionally fold b517002093 to apply the

same 0xFF -> 0xFFL fix to the parallel helper

Conversions.byteArrayToLong() in

java/org/apache/catalina/util/Conversions.java, which is the

helper used by the legacy WsFrame parser; without it the new

< 0 check in the legacy parser would falsely reject legitimate

large frames. Backport of upstream commits f9f75c14, 34d19fbe24,

4c04982870 and b517002093

(https://github.com/apache/tomcat/commit/f9f75c14

https://github.com/apache/tomcat/commit/34d19fbe24

https://github.com/apache/tomcat/commit/4c04982870

https://github.com/apache/tomcat/commit/b517002093)

  • CVE-2020-13935

Affected software

CLSA-2026-1777446601 is recorded against 9 packages.

  • libservlet3.0-java (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)
  • libservlet3.0-java-doc (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)
  • libtomcat7-java (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)
  • tomcat7 (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)
  • tomcat7-admin (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)
  • tomcat7-common (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)
  • tomcat7-docs (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)
  • tomcat7-examples (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)
  • tomcat7-user (fixed in 7.0.68-1ubuntu0.4+tuxcare.els7)

Timeline and source

Published on 29 April 2026 and last revised on 4 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

errata.tuxcare.com (Advisory)

Other advisories for this package

libservlet3.0-java has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-04-29
Updated 2026-08-20
Modified 2026-06-04
Fix URL N/A

Affected Packages

Software From version Fixed in
libservlet3.0-java 7.0.68-1ubuntu0.4+tuxcare.els7
libservlet3.0-java-doc 7.0.68-1ubuntu0.4+tuxcare.els7
libtomcat7-java 7.0.68-1ubuntu0.4+tuxcare.els7
tomcat7 7.0.68-1ubuntu0.4+tuxcare.els7
tomcat7-admin 7.0.68-1ubuntu0.4+tuxcare.els7
tomcat7-common 7.0.68-1ubuntu0.4+tuxcare.els7
tomcat7-docs 7.0.68-1ubuntu0.4+tuxcare.els7
tomcat7-examples 7.0.68-1ubuntu0.4+tuxcare.els7
tomcat7-user 7.0.68-1ubuntu0.4+tuxcare.els7

Free Vulnerability Check

Is your site affected by CLSA-2026-1777446601?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CLSA-2026-1777446601 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesChainguardChainguard 2026