Security readout for executives and security teams
Plain-English summary
pacparser is a library for evaluating proxy auto-configuration logic. In versions through 1.3.x, a local user can trigger a buffer overflow through URL handling. Business risk is limited by the local attack requirement, but affected embedded uses should be upgraded because memory corruption can affect confidentiality, integrity, and availability.
Executive priority
Treat this as a moderate maintenance and dependency-risk item. It is not shown as internet-exploited or KEV-listed, but memory corruption in a shared library can create broader risk when embedded in operational software.
Technical view
CVE-2019-25078 affects pacparser 1.0 through 1.3.x. The issue is a CWE-119 buffer overflow in pacparser_find_proxy in src/pacparser.c caused by the url argument. CVSS 3.1 is 5.3 with local access, low complexity, low privileges, no user interaction, and limited C/I/A impact.
Likely exposure
Exposure is most likely where pacparser is installed directly, bundled into applications, or vendored into proxy/PAC handling workflows. Public-facing exposure is not indicated by the sources because local access is required.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. The source bundle states local attack is required, with low privileges and no user interaction in the CVSS vector.
Researcher notes
The sources identify the affected function, file, argument, version range, CVSS vector, CWE-119, and fixed release. They do not provide evidence of remote reachability, active exploitation, or downstream product impact, so those points should be verified per environment.
Mitigation direction
- Upgrade pacparser to version 1.4.0 or later.
- Apply or verify inclusion of patch commit 853e8f45607cb07b877ffd270c63dbcdd5201ad9.
- Replace bundled or vendored pacparser copies in dependent applications.
- Check vendor or application maintainer guidance for packaged distributions.
- Limit local access to systems processing untrusted PAC URLs where upgrade is delayed.
Validation and detection
- Inventory package managers, SBOMs, and source trees for pacparser versions 1.0 through 1.3.x.
- Confirm deployed binaries or containers include pacparser 1.4.0 or the named patch.
- Review applications that embed PAC parsing rather than linking a system pacparser package.
- Verify change management records cover dependent products that bundle pacparser.
- Track vendor advisories for downstream packages that may carry older pacparser code.
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-119: 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-2019-25078 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
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L1.83.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/manugarg/pacparser/issues/99CVE reference
- https://github.com/manugarg/pacparser/releases/tag/v1.4.0CVE reference
- https://github.com/manugarg/pacparser/commit/853e8f45607cb07b877ffd270c63dbcdd5201ad9CVE reference
- https://vuldb.com/?id.215443CVE 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 Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.