CVE-2025-27508: Emissary Emissary May Use A Broken Vulnerability

HIGH
Advisory Identifier: GHSA-hw43-fcmm-3m5g
CVSS 7.5
CWE-327
Published
Advisory Summary

CVE-2025-27508 is a HIGH (CVSS 7.5) emissary may use a broken vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Emissary libraries in the Maven ecosystem. The issue involves emissary may use a broken or risky cryptographic algorithm. Remediation is available by upgrading affected packages to version 8.24.0.

CVE-2025-27508 at a Glance

CVE Identifier CVE-2025-27508
GHSA Identifier GHSA-hw43-fcmm-3m5g
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Emissary
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-27508

To remediate this vulnerability, upgrade all affected Emissary dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

gov.nsa.emissary:emissary fixed: 8.24.0
<dependency>
    <groupId>gov.nsa.emissary</groupId>
    <artifactId>emissary</artifactId>
    <version>8.24.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=gov.nsa.emissary

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-27508, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=gov.nsa.emissary

Analyze the terminal output to locate any version of Emissary in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 8.24.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=gov.nsa.emissary command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Emissary, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The ChecksumCalculator class within allows for hashing and checksum generation, but it includes or defaults to algorithms that are no longer recommended for secure cryptographic use cases (e.g., SHA-1, CRC32, and SSDEEP). These algorithms, while possibly valid for certain non-security-critical tasks, can expose users to security risks if used in scenarios where strong cryptographic guarantees are required. ### Requirement from NIST Requirement from NIST regarding SHA1 https://csrc.nist.gov/projects/hash-functions#:~:text=NIST%20deprecated%20the%20use%20of,use%20of%20the%20SHA%2D1. > Federal agencies should use SHA-2 or SHA-3 as an alternative to SHA-1. > Further guidance will be available soon. Send questions on the transition to sha-1-transition@nist.gov. https://www.nist.gov/news-events/news/2022/12/nist-retires-sha-1-cryptographic-algorithm ### Mitigation and Fix Make it clear to developers and users that the ChecksumCalculator is specific to the "Known File Filter" (KFF) document similarity feature and is not intended to suggest or endorse global use as a cryptographically secure hashing or checksum mechanism. While these specific default insecure algorithms can not be updated without violating the intended use-case, it can be clearly documented and prevented using better access modifiers in the ChecksumCalculator class. ### Details Within ChecksumCalculator.java, the following points raise potential security concerns: SHA-1: SHA-1 has been widely deprecated for cryptographic purposes due to known collision attacks. The constructor defaults to "SHA-1" if no specific algorithm is provided. CRC32: CRC32 is a simple checksum mechanism, not a cryptographic hash function. It is unsuitable for security-critical integrity checks since it can be easily manipulated or collided. SSDEEP (Fuzzy Hashing): SSDEEP is a context-specific tool used for similarity matching and may not be a secure cryptographic function for authentication or tamper detection. There is no apparent mechanism to prevent developers from using these weaker algorithms in security-sensitive contexts. Users of emissary who rely on ChecksumCalculator for strong security guarantees (e.g., data integrity or authentication) may be misled into assuming these algorithms provide adequate protection. ### PoC Code could be found https://github.com/NationalSecurityAgency/emissary/blob/main/src/main/java/emissary/kff/ChecksumCalculator.java ### Impact Impact Weakened Security Posture: Applications integrating Emissary may inadvertently use these algorithms in a way that could be exploited (e.g., collisions in SHA-1, trivial collisions in CRC32). Misleading Assurance: Developers might assume Emissary’s recommended defaults are secure for cryptographic validation, which can result in insecure implementations. Potential for Collision Attacks: Attackers could craft inputs that yield the same SHA-1 hash or manipulate CRC32 sums, thus bypassing naive integrity checks. Because this project is produced under the NSA umbrella, users may have an inflated trust in its security posture, potentially leading them to rely on these algorithms in high-security environments without recognizing the associated risks.

CVE-2025-27508 Affected Emissary Versions

1 component(s)
Fixed Versions:
8.24.0
Product / Package Ecosystem Affected Versions Fixed Version
gov.nsa.emissary:emissary
Maven
< 8.24.0
8.24.0

References

Frequently Asked Questions

What is CVE-2025-27508?
CVE-2025-27508 is a security vulnerability in Emissary involving Emissary May Use a Broken or Risky Cryptographic Algorithm under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Emissary versions are affected?
Affected versions include releases prior to 8.24.0 across affected packages: gov.nsa.emissary:emissary.
What version fixes CVE-2025-27508?
Upgrading to 8.24.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is emissary affected?
Yes, gov.nsa.emissary:emissary is affected in releases prior to 8.24.0. Upgrade your dependency to 8.24.0 or later.
What is the CVSS score of CVE-2025-27508?
CVE-2025-27508 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2025-27508?
CVE-2025-27508 is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check Maven dependencies for CVE-2025-27508?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=gov.nsa.emissary'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hw43-fcmm-3m5g",
  "modified" : "2025-03-06T01:33:29Z",
  "published" : "2025-03-05T22:18:51Z",
  "aliases" : [ "CVE-2025-27508" ],
  "summary" : "Emissary May Use a Broken or Risky Cryptographic Algorithm",
  "details" : "### Summary\nThe ChecksumCalculator class within  allows for hashing and checksum generation, but it includes or defaults to algorithms that are no longer recommended for secure cryptographic use cases (e.g., SHA-1, CRC32, and SSDEEP). These algorithms, while possibly valid for certain non-security-critical tasks, can expose users to security risks if used in scenarios where strong cryptographic guarantees are required.\n\n### Requirement from NIST\nRequirement from NIST regarding SHA1\n\nhttps://csrc.nist.gov/projects/hash-functions#:~:text=NIST%20deprecated%20the%20use%20of,use%20of%20the%20SHA%2D1.\n\n> Federal agencies should use SHA-2 or SHA-3 as an alternative to SHA-1.\n> Further guidance will be available soon. Send questions on the transition to sha-1-transition@nist.gov.\n\nhttps://www.nist.gov/news-events/news/2022/12/nist-retires-sha-1-cryptographic-algorithm\n\n### Mitigation and Fix\nMake it clear to developers and users that the ChecksumCalculator is specific to the \"Known File Filter\" (KFF) document similarity feature and is not intended to suggest or endorse global use as a cryptographically secure hashing or checksum mechanism.\n\nWhile these specific default insecure algorithms can not be updated without violating the intended use-case, it can be clearly documented and prevented using better access modifiers in the ChecksumCalculator class.\n\n### Details\nWithin ChecksumCalculator.java, the following points raise potential security concerns:\n\nSHA-1:\nSHA-1 has been widely deprecated for cryptographic purposes due to known collision attacks.\nThe constructor defaults to \"SHA-1\" if no specific algorithm is provided.\nCRC32:\nCRC32 is a simple checksum mechanism, not a cryptographic hash function. It is unsuitable for security-critical integrity checks since it can be easily manipulated or collided.\nSSDEEP (Fuzzy Hashing):\nSSDEEP is a context-specific tool used for similarity matching and may not be a secure cryptographic function for authentication or tamper detection.\nThere is no apparent mechanism to prevent developers from using these weaker algorithms in security-sensitive contexts. Users of emissary who rely on ChecksumCalculator for strong security guarantees (e.g., data integrity or authentication) may be misled into assuming these algorithms provide adequate protection.\n\n### PoC\nCode could be found https://github.com/NationalSecurityAgency/emissary/blob/main/src/main/java/emissary/kff/ChecksumCalculator.java\n\n### Impact\nImpact\nWeakened Security Posture: Applications integrating Emissary may inadvertently use these algorithms in a way that could be exploited (e.g., collisions in SHA-1, trivial collisions in CRC32).\nMisleading Assurance: Developers might assume Emissary’s recommended defaults are secure for cryptographic validation, which can result in insecure implementations.\nPotential for Collision Attacks: Attackers could craft inputs that yield the same SHA-1 hash or manipulate CRC32 sums, thus bypassing naive integrity checks.\nBecause this project is produced under the NSA umbrella, users may have an inflated trust in its security posture, potentially leading them to rely on these algorithms in high-security environments without recognizing the associated risks.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "gov.nsa.emissary:emissary"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.24.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 8.23.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/NationalSecurityAgency/emissary/security/advisories/GHSA-hw43-fcmm-3m5g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-27508"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/NationalSecurityAgency/emissary/commit/da3a81a8977577597ff2a944820a5ae4e9762368"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/NationalSecurityAgency/emissary"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/NationalSecurityAgency/emissary/releases/tag/8.24.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-05T22:18:51Z",
    "nvd_published_at" : "2025-03-05T22:15:35Z"
  }
}