LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000338: In Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully validate ASN.1 encoding of si...

In Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects older Bouncy Castle Java cryptography code. A DSA signature could be accepted even when its ASN.1 structure contains extra data. That can undermine trust in signed objects by allowing data to be present without being covered as expected by the signature.

Executive priority

Treat as a targeted integrity risk, not an emergency based on the provided evidence. Prioritize remediation where older Bouncy Castle validates signed business, identity, update, or configuration data.

Technical view

Bouncy Castle JCE Provider 1.55 and earlier did not fully validate ASN.1 encoding during DSA signature verification. Extra elements in the signature sequence could be ignored while verification still succeeds, potentially allowing hidden or unexpected data in signed structures.

Likely exposure

Exposure is most likely in Java applications or platforms that use Bouncy Castle JCE Provider 1.55 or earlier for DSA signature verification, including downstream packaged versions referenced by Debian, Red Hat, Ubuntu, Oracle, and NetApp advisories.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The risk is integrity-focused and depends on whether an application trusts DSA signatures over ASN.1-encoded structures where hidden data could matter.

Researcher notes

The source record identifies a parser validation weakness but provides no CVSS, CWE, or exploit evidence. Analysis should focus on library reachability: affected version present, JCE provider loaded, DSA verification path used, and signed ASN.1 data security-relevant.

Mitigation direction

  • Inventory Java applications and packaged dependencies for Bouncy Castle JCE Provider 1.55 or earlier.
  • Apply vendor security updates from the relevant OS, appliance, or application supplier.
  • Upgrade bundled Bouncy Castle libraries according to upstream or vendor guidance.
  • Prioritize systems that verify signed documents, tokens, messages, or configuration artifacts.
  • Retest signature validation workflows after updating the cryptography provider.

Validation and detection

  • Check dependency manifests, shaded JARs, and runtime classpaths for Bouncy Castle versions.
  • Confirm whether DSA signature verification is used on ASN.1-encoded signed structures.
  • Review vendor advisories for fixed package availability in your distribution or product.
  • Verify deployed versions changed after patching, not only build-time dependencies.
  • Check security scans for remaining CVE-2016-1000338 findings.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-1000338 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.