# CVE-2022-32777: Information disclosure in AVideo

> Missing HttpOnly and Secure flags on session cookies allow attackers to steal session data via JavaScript or non-HTTPS connections, leading to account takeover.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-7pq2-hg75-vrf6

## What is CVE-2022-32777?

CVE-2022-32777 is a high-severity vulnerability in Wwbn Avideo, published on 22 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2022-32777?

It affects 1 product.


Products: Wwbn Avideo.

## How do I fix CVE-2022-32777?

No fix has been published for CVE-2022-32777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-32777 being exploited?

There is no known exploitation of CVE-2022-32777 in the wild and no public exploit code.

## Other vulnerabilities in Wwbn Avideo

- [CVE-2026-40911](https://insights.sbomify.com/CVE-2026-40911/): WWBN AVideo YPTSocket WebSocket Broadcast Relay Leads to Unauthenticated Cross-User JavaScript Execution via Client-Side eval() Sinks (critical 10.0)
- [CVE-2026-33478](https://insights.sbomify.com/CVE-2026-33478/): AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection (critical 10.0)
- [CVE-2022-30534](https://insights.sbomify.com/CVE-2022-30534/): Command injection in AVideo (critical 9.9)
- [CVE-2022-30547](https://insights.sbomify.com/CVE-2022-30547/): Path traversal in AVideo (critical 9.9)
- [CVE-2022-32572](https://insights.sbomify.com/CVE-2022-32572/): Command injection in AVideo (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-32777 and fix it if it is affected.

What it is: CVE-2022-32777 is a high-severity vulnerability in Wwbn Avideo, published on 22 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-32777 in the wild and no public exploit code.

Affected product: Wwbn Avideo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-32777/ (Markdown: https://insights.sbomify.com/CVE-2022-32777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-32777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-32777
- OSV: https://osv.dev/vulnerability/CVE-2022-32777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-32777/
Summaries are generated and may contain mistakes; the official description above is the record.