Skip to content
Noroxi
CVE-2013-6427· NVD / CVE Program· CNA redhat

upgrade.py in the hp-upgrade service in HP Linux Imaging and Printing (HPLIP) 3.x through 3.13.11 launches a program from an http URL, which

upgrade.py in the hp-upgrade service in HP Linux Imaging and Printing (HPLIP) 3.x through 3.13.11 launches a program from an http URL, which allows man-in-the-middle attackers to execute arbitrary code by gaining control over the client-server data stream.

MediumCVSS 6.8 · v2.0—No exploit Fix available
Published
Dec 9, 2013
Updated
Jun 16, 2026
EPSS
4.0% · 90th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.0%

Affected systems

VendorProduct
hplinux imaging and printing project

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • hp linux imaging and printing project3.10.2
  • hp linux imaging and printing project3.10.5
  • hp linux imaging and printing project3.10.6
  • hp linux imaging and printing project3.10.9
  • hp linux imaging and printing project3.11.1
  • hp linux imaging and printing project3.11.10
  • hp linux imaging and printing project3.11.12
  • hp linux imaging and printing project3.11.3
  • hp linux imaging and printing project3.11.3a
  • hp linux imaging and printing project3.11.5
  • hp linux imaging and printing project3.11.7
  • hp linux imaging and printing project3.12.10
  • hp linux imaging and printing project3.12.11
  • hp linux imaging and printing project3.12.2
  • hp linux imaging and printing project3.12.4
  • hp linux imaging and printing project3.12.6
  • hp linux imaging and printing project3.12.9
  • hp linux imaging and printing project3.13.10
  • hp linux imaging and printing project3.13.2
  • hp linux imaging and printing project3.13.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12hplipbefore 3.13.11-23.13.11-2
Debian:6.0hplipbefore 3.10.6-2+squeeze23.10.6-2+squeeze2
Debian:7hplipbefore 3.12.6-3.1+deb7u13.12.6-3.1+deb7u1
openSUSE:Tumbleweedhplipbefore 3.16.10-1.13.16.10-1.1

Same product

hp: all records

Other highest-scoring records for the same primary product.

  • CVE-2007-5208hpssd in Hewlett-Packard Linux Imaging and Printing Project (hplip) 1.x and 2.x before 2.7.10 allows context-dependent attackers to execute
    50Plan
  • CVE-2010-4267Stack-based buffer overflow in the hpmud_get_pml function in io/hpmud/pml.c in Hewlett-Packard Linux Imaging and Printing (HPLIP) 1.6.7, 3.9
    33Monitor
  • CVE-2011-2697foomatic-rip-hplip in HP Linux Imaging and Printing (HPLIP) 3.11.5 allows remote attackers to execute arbitrary code via a crafted *Foomatic
    30Monitor
  • CVE-2008-2940The alert-mailing implementation in HP Linux Imaging and Printing (HPLIP) 1.6.7 allows local users to gain privileges and send e-mail messag
    28Monitor
  • CVE-2013-4325The check_permission_v1 function in base/pkit.py in HP Linux Imaging and Printing (HPLIP) through 3.13.9 does not properly use D-Bus for com
    27Monitor
  • CVE-2008-2941The hpssd message parser in hpssd.py in HP Linux Imaging and Printing (HPLIP) 1.6.7 allows local users to cause a denial of service (process
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:hplip3.13.11-2 · Debian:12Package registry (OSV)
opensuse:hplip3.16.10-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    P · data or configuration can be modified
    Availability
    P · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    P
    Availability impact
    P

    Weakness class (CWE)

    CWE-94 · Improper Control of Generation of Code ('Code Injection')

    CVSS vector

    AV:N/AC:M/Au:N/C:P/I:P/A:P

    nvd-primary

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records