Skip to main content

Insufficient data authenticity validation - JAR signing

Description​

The JAR files that compose the application are not correctly signed, allowing an attacker to modify the code withouth raising alerts on an integrity check.

Impact​

Inject malicious code in the application without raising alerts.

Recommendation​

Sign the application JAR files using a trusted key.

Threat​

Anonymous attacker from Internet with access to the JAR Files.

Expected Remediation Time​

⌚ 90 minutes.

Score​

Default score using CVSS 3.1. It may change depending on the context of the vulnerability.

Base​

  • Attack vector: N
  • Attack complexity: H
  • Privileges required: N
  • User interaction: N
  • Scope: U
  • Confidentiality: N
  • Integrity: L
  • Availability: N

Temporal​

  • Exploit code madurity: X
  • Remediation level: O
  • Report confidence: C

Result​

  • Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:X/RL:O/RC:C
  • Score:
    • Base: 3.7
    • Temporal: 3.6
  • Severity:
    • Base: Low
    • Temporal: Low

Code Examples​

Compliant code​

Sign all the JAR files of the application with a certified key tool

jarsigner -keystore NONE -certchain "bundle.pem" -tsa "http://time.certum.pl" -storetype PKCS11
  -providerClass sun.security.pkcs11.SunPKCS11 -providerArg "provider.cfg"
  -storepass "[your_pin]" "[your_code].jar" "[your_alias]"

Non compliant code​

The source code has .jar files that were not signed before runtime, please check to verify before compiling

Requirements​