LiveActive security incident?Get immediate response
CVE Record

CVE-2019-1010263: Perl Crypt::JWT prior to 0.023 is affected by: Incorrect Access Control.

Perl Crypt::JWT prior to 0.023 is affected by: Incorrect Access Control. The impact is: allow attackers to bypass authentication by providing a token by crafting with hmac(). The component is: JWT.pm, line 614. The attack vector is: network connectivity. The fixed version is: after commit b98a59b42ded9f9e51b2560410106207c2152d6c.

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

Security readout for executives and security teams

Plain-English summary

Crypt::JWT is a Perl library for JSON Web Tokens. Versions before 0.023 had an access-control flaw that could let an attacker bypass authentication by supplying a specially crafted token. Business impact depends on whether affected applications rely on this library for login, API, or service-to-service authorization decisions.

Executive priority

Treat as high priority where Crypt::JWT protects customer access, administrative functions, or exposed APIs. If the library is unused or only present in non-authentication code, urgency is lower but still warrants cleanup.

Technical view

CVE-2019-1010263 affects Perl Crypt::JWT prior to 0.023. The CVE describes incorrect access control in JWT.pm around line 614, involving hmac() token handling. The stated attack vector is network connectivity, and the fix is after commit b98a59b42ded9f9e51b2560410106207c2152d6c.

Likely exposure

Exposure is likely limited to Perl applications or services using Crypt::JWT before 0.023 to validate JWTs for authentication or authorization. Internet-facing APIs and identity-adjacent services would carry the highest business risk.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVE states attackers could bypass authentication by providing a crafted token over the network, but no exploit prevalence or real-world campaign data is provided.

Researcher notes

Evidence is sparse: no CVSS, CWE, or KEV status is provided. The strongest technical anchors are the CVE description, Openwall reference, affected version statement, and GitHub fixing commit. Validate actual application use before assigning enterprise-wide exposure.

Mitigation direction

  • Upgrade Crypt::JWT to version 0.023 or later.
  • Confirm deployed packages include the referenced fixing commit.
  • Prioritize services where JWTs gate login, APIs, or privileged actions.
  • Review vendor and maintainer guidance for any additional hardening recommendations.

Validation and detection

  • Inventory Perl applications using Crypt::JWT and record deployed versions.
  • Check dependency manifests, lockfiles, and runtime package inventories for versions before 0.023.
  • Map affected library use to authentication and authorization paths.
  • Confirm production deployments run the upgraded package or fixed commit.
  • Review authentication logs for unusual token validation failures or bypass indicators.
Prepared
Confidence
medium
Sources
4

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-1010263 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
3Source 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
Perl Crypt::JWTPerl Crypt::JWTprior to 0.023 [fixed: after commit b98a59b42ded9f9e51b2560410106207c2152d6c]Listed
Weakness

CWE details

No CWE listed

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