CVE-2019-1010263
No exploitation reported by the sources we read.
- Published2019-07-17
- WeaknessCWE-347
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2019-07-1721:15CVE publishedNVD
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | = jwt_project | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- libcrypt-jwt-perlUbuntu:26.10all versions · no fixed version listed
- libcrypt-jwt-perlUbuntu:26.04:LTSall versions · no fixed version listed
- libcrypt-jwt-perlUbuntu:25.10all versions · no fixed version listed
- libcrypt-jwt-perlUbuntu:24.04:LTSall versions · no fixed version listed
- libcrypt-jwt-perlUbuntu:22.04:LTSall versions · no fixed version listed
- libcrypt-jwt-perlUbuntu:20.04:LTSall versions · no fixed version listed
Fix
Advisories and patches
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-347read 2026-10-23
- FIRST EPSSEPSS score1.3 %2026-11-18
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2019-2002same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-54vx-xvq8-jh85same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2019-07-17
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-54vx-xvq8-jh85
Frequently asked questions
What is CVE-2019-1010263?
Is CVE-2019-1010263 actively exploited?
What is the CVSS score for CVE-2019-1010263?
Running libcrypt-jwt-perl? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-54vx-xvq8-jh85
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served