CVE-2022-32777
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 · uneditedAn information disclosure vulnerability exists in the cookie functionality of WWBN AVideo 11.6 and dev master commit 3f7c0364. The session cookie and the pass cookie miss the HttpOnly flag, making them accessible via JavaScript. The session cookie also misses the secure flag, which allows the session cookie to be leaked over non-HTTPS connections. This could allow an attacker to steal the session cookie via crafted HTTP requests.This vulnerabilty is for the session cookie which can be leaked via JavaScript.
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 confidenceThe session cookie and pass cookie in WWBN AVideo 11.6 and dev master commit 3f7c0364 lack the HttpOnly flag, allowing them to be accessed via JavaScript and potentially stolen through XSS. Additionally, the session cookie lacks the Secure flag, enabling leakage over unencrypted HTTP connections.
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= 11.6CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 AVideo versionCheck the installed version of WWBN AVideo by examining the version file, about page, or admin panel. Look for version 11.6 or a dev master build.Affected if The installed version is 11.6 or the codebase corresponds to dev master around commit 3f7c0364
-
Capture session cookie headersLog into the AVideo application and inspect the Set-Cookie HTTP response headers for the session cookie. Use browser developer tools (Application/Storage tab) or a proxy to capture the response headers.Affected if The Set-Cookie header for the session cookie does not include the HttpOnly flag, or does not include the Secure flag
-
Capture pass cookie headersAfter authentication, inspect the Set-Cookie HTTP response headers specifically for any cookie named 'pass' or containing password-related data.Affected if The Set-Cookie header for the pass cookie does not include the HttpOnly flag, allowing JavaScript access to the cookie value
-
Verify cookie flags via browser consoleOpen browser developer tools, go to the Application (Chrome) or Storage (Firefox) tab, expand Cookies for the site domain, and inspect the session and pass cookies. Check the attributes column for HttpOnly and Secure flags.Affected if The session cookie shows no HttpOnly or no Secure flag, or the pass cookie shows no HttpOnly flag
If running AVideo version 11.6 and either the session cookie or pass cookie is accessible without HttpOnly flag, or the session cookie lacks Secure flag, the environment is affected by this CVE.
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 dataConfigure the session and pass cookies with the HttpOnly and Secure flags to prevent JavaScript access and ensure transmission only over HTTPS.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32777 — 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-2022-32777 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