dbcve.org
ProxygenApplication · Proxygen Project

CVE-2015-7263

HIGH · 7.5 CVSS v3.0 Published 2017-04-10
Fix available
A fix is available. Upgrade to after 0.32.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The SPDY/2 codec in Facebook Proxygen before 2015-11-09 allows remote attackers to conduct hijacking attacks and bypass ACL checks via a crafted host value.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SPDY/2 codec in Facebook Proxygen fails to properly validate crafted host values, allowing remote attackers to bypass ACL (Access Control List) checks and conduct session hijacking attacks.

MitigationUpgrade Proxygen to version 2015-11-09 or later, which contains the patched SPDY/2 codec with proper host value validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ProxygenApplication
Affected:<= 0.32.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Proxygen installation
    Check for Proxygen installation by searching for proxygen binaries, libraries, or headers (e.g., locate proxygen, find /usr -name '*proxygen*', or check package manager listings)
    Affected if Proxygen is not installed on the system
  2. Determine Proxygen version
    Run proxygen --version or check the installed package version (dpkg -l | grep proxygen, rpm -qi proxygen, or similar package manager query)
    Affected if The installed version is 0.32.0 or earlier
  3. Verify SPDY/2 protocol support
    Inspect Proxygen configuration files for SPDY/2 protocol enablement, or check if the server responds to SPDY/2 upgrade requests using tools like curl with SPDY support or Wireshark capture
    Affected if SPDY/2 protocol support is enabled or actively used
  4. Check for ACL configurations
    Review Proxygen configuration for Access Control List rules (look for ACL, access-control, allow, deny directives in proxygen.conf or similar config files)
    Affected if ACL rules are defined in the Proxygen configuration

The environment is affected if Proxygen version 0.32.0 or earlier is installed with SPDY/2 enabled and ACL rules are configured, as the host validation flaw allows bypassing those ACLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.32.0
Interim mitigation

Upgrade Proxygen to version 2015-11-09 or later, which contains the patched SPDY/2 codec with proper host value validation.

Fix this in Proxygen Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7263 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-7263 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data