Security readout for executives and security teams
Plain-English summary
Some Perl applications may think encrypted data has been authenticated when it has not. In CryptX before 0.062, two decrypt-and-verify functions reportedly do not verify the authentication tag. If an exposed workflow trusts those functions, tampered encrypted data could be accepted as valid.
Executive priority
Treat as high urgency for any Perl system using CryptX for authenticated encryption. The business risk is silent trust failure in encrypted-data workflows, but exposure must be confirmed because the sources do not name affected products.
Technical view
CVE-2018-25099 affects the Perl CryptX module before 0.062. gcm_decrypt_verify() and chacha20poly1305_decrypt_verify() do not verify the authentication tag, undermining authenticated encryption guarantees. The record maps this to CWE-347 and assigns CVSS 3.1 score 9.8, network reachable with no privileges or user interaction.
Likely exposure
Exposure is likely limited to Perl services or tools that depend on CryptX before 0.062 and call the named AEAD decrypt-verify functions. The source bundle does not identify specific downstream products, CPEs, or deployment patterns.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Practical impact depends on whether attackers can supply encrypted inputs to application paths that use the affected functions and then trust the decrypted result.
Researcher notes
Focus review on callers of the two named functions in CryptX before 0.062. Assess attacker control over ciphertext inputs, trust decisions after decryption, and whether application-layer validation limits impact. Avoid assuming active exploitation without external evidence.
Mitigation direction
- Upgrade CryptX to version 0.062 or later where feasible.
- Prioritize internet-facing or partner-facing services accepting encrypted client input.
- Check the CryptX changelog and maintainer guidance before release.
- Add regression tests proving tampered authentication tags are rejected.
- Review any compensating validation around decrypted data.
Validation and detection
- Inventory Perl applications and dependency manifests for CryptX usage.
- Confirm deployed CryptX versions are 0.062 or later.
- Search code for gcm_decrypt_verify() and chacha20poly1305_decrypt_verify().
- Verify affected paths handle authentication failure explicitly.
- Review tests covering invalid or modified AEAD tags.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2018-25099 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/DCIT/perl-CryptX/issues/47CVE reference
- https://github.com/libtom/libtomcrypt/pull/451CVE reference
- https://metacpan.org/dist/CryptX/changesCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.