vex-reader
Utility to read Red Hat VEX files that are located at https://access.redhat.com/security/data/csaf/v2/vex/.
I'm (slowly) aiming to make this a bit more extensible so that it can be used with other VEX files beyond just Red Hat, but I'm basing all of this off of Red Hat VEX files to aim to make this a proper parsing library for any VEX documents.
Installation
Requires Python 3.10 or later.
Install vex-reader from PyPI:
pip install vex-reader
Or with uv:
uv pip install vex-reader
Usage
The best way to use vex-reader is to install the Python module. It provides
the vex-reader binary and you can import the library for use in your own
applications.
vex-reader --vex /path/to/advisory.json
CVE-2002-2443
-------------
Public on : 2002-06-15
Impact : Moderate
CVSS Score: 5.0
Vulnerability summary
krb5: UDP ping-pong flaw in kpasswd
Vulnerability description
schpw.c in the kpasswd service in kadmind in MIT Kerberos 5 (aka krb5) before 1.11.3 does not properly validate UDP packets before
sending responses, which allows remote attackers to cause a denial of service (CPU and bandwidth consumption) via a forged packet that
triggers a communication loop, as demonstrated by krb_pingpong.nasl, a related issue to CVE-1999-0103.
CVSS score applicability
The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational
purposes to better understand the severity of this vulnerability.
Terms of Use
This content is licensed under the Creative Commons Attribution 4.0 International License
(https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide
attribution to Red Hat Inc. and provide a link to the original.
Additional Information
Bugzilla: 962531
External References
https://bugzilla.redhat.com/show_bug.cgi?id=962531
https://www.cve.org/CVERecord?id=CVE-2002-2443
https://nvd.nist.gov/vuln/detail/CVE-2002-2443
Red Hat affected packages and issued errata
RHSA-2013:0942 -- Red Hat Enterprise Linux Workstation (v. 6)
CVSS v2 Vector
Red Hat: AV:N/AC:L/Au:N/C:N/I:N/A:P
NVD : AV:N/AC:L/Au:N/C:N/I:N/A:P
CVSS v2 Score Breakdown
Red Hat NVD
CVSS v2 Base Score 5.0 5.0
Access Vector Network Network
Access Complexity Low Low
Authentication None None
Confidentiality Impact None None
Integrity Impact None None
Availability Impact Partial Partial
Copyright © Red Hat, Inc. All rights reserved
By default, vex-reader will pull the CVSS score from NVD's API. If this
is undesirable (for testing, etc.) you can pass the --no-nvd argument to
prevent lookups. Currently, vex-reader requires the VEX file to parse to
be on-disk.
A good place to find VEX documents is https://wid.cert-bund.de/.well-known/csaf-aggregator/aggregator.json
License
GPLv3+. See LICENSE.
Changelog
See CHANGELOG.md.
Contributing
Development setup, releasing, and Trusted Publishing notes: docs/DEVELOPMENT.md.
Running tests: docs/TESTING.md.
Security reports: SECURITY.md.
Metadata
Release files for vex-reader 0.9.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vex_reader-0.9.5.2.tar.gz | 56.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vex_reader-0.9.5.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 100.0 kB
Release files / vex_reader-0.9.5.2.tar.gz
| Download URL | vex_reader-0.9.5.2.tar.gz |
|---|---|
| Size | 56.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f5350b82c3007ce1b403e1d5ed115453dccad901c9474412745e534ea63843b
|
|
BLAKE2b-256 checksum How to use checksums |
754b355d7ebf104a26adcab224be7912affce59eaa35e11828cbaaadcf7e8e4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logRelease files / vex_reader-0.9.5.2-py3-none-any.whl
| Download URL | vex_reader-0.9.5.2-py3-none-any.whl |
|---|---|
| Size | 43.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4620448cabe7bc6d46a4fd57a725f43cb41fa2737f5487010530c48021bce98a
|
|
BLAKE2b-256 checksum How to use checksums |
23849e8e3b44d3a0e8593835b2551efc2da9e920073517f81afb67977f14db79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logSecurity for vex-reader 0.9.5.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for vex_reader-0.9.5.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.