CVE-2015-7265
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 · uneditedFacebook Proxygen before 2015-11-09 mismanages HTTPMessage.request state, which allows remote attackers to conduct hijacking attacks and bypass ACL checks.
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 · moderate confidenceFacebook Proxygen, a C++ HTTP library, contains a state management flaw in HTTPMessage.request handling before November 9, 2015. The vulnerability allows remote attackers to manipulate request state, enabling session hijacking and bypassing ACL (Access Control List) checks.
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<= 0.32.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Proxygen installationLocate the Proxygen library in your environment by searching for proxygen header files (e.g., HTTPMessage.h) or the compiled library binary. Check build artifacts, package managers, or dependency manifests for proxygen version information.Affected if Proxygen version 0.32.0 or earlier is found installed or referenced in dependencies
-
Confirm HTTPMessage.request usageSearch codebase for includes of proxygen/lib/http/HTTPMessage.h and any code paths that access or modify the request object (e.g., HTTPMessage::getRequest(), HTTPMessage::setRequest(), or similar methods).Affected if Code actively uses HTTPMessage request handling methods from the proxygen library
-
Identify ACL/authentication dependenciesReview authentication and authorization code that relies on HTTP request state - inspect any logic that checks session tokens, user credentials, or ACL rules using data from HTTPMessage::getRequest() or related request accessors.Affected if Authentication or ACL logic depends on request state from Proxygen's HTTPMessage without additional validation
-
Check for request state manipulation vectorsAudit code paths where HTTP request headers, cookies, or session identifiers are parsed or modified. Look for any code that could allow an attacker to influence request state after initial parsing.Affected if Request parsing logic allows external input to modify request state after initial handling
You are affected if Proxygen version 0.32.0 or earlier is in use AND your application relies on HTTPMessage request handling for authentication or ACL decisions.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Proxygen to version 2015-11-09 or later. Audit all authentication and authorization logic that depends on HTTP request state to ensure no bypass vectors remain.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7265 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7265 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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