CVE-2024-1965
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 · uneditedServer-Side Request Forgery vulnerability in Haivision's Aviwest Manager and Aviwest Steamhub. This vulnerability could allow an attacker to enumerate internal network configuration without the need for credentials. An attacker could compromise an internal server and retrieve requests sent by other users.
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 confidenceServer-Side Request Forgery (SSRF) vulnerability in Haivision's Aviwest Manager and Aviwest Streamhub allows unauthenticated attackers to make the server perform arbitrary HTTP requests to internal or external resources. This enables internal network enumeration and the ability to intercept requests sent by other users, potentially compromising internal infrastructure.
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 dataall versionsall versionsCVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Haivision product installationSearch for 'haivision', 'aviwest', 'streamhub', or 'manager' in installed applications list, running processes, or service names on the systemAffected if Any Haivision Aviwest Manager or Streamhub software is found running on the system
-
Confirm product typeAccess the web interface or check process/service details to identify whether the installed product is Manager or StreamhubAffected if The product is identified as Haivision Aviwest Manager or Haivision Streamhub
-
Verify web interface exposureCheck if the Haivision web management interface is accessible on network ports (typically 80/443 or configured custom ports)Affected if The Haivision web interface is reachable over the network
-
Review for SSRF indicatorsExamine HTTP access logs, proxy logs, or network traffic for requests originating from the Haivision server to unusual internal or external URLs, especially internal IP addresses or private network rangesAffected if The server has made HTTP requests to internal infrastructure (e.g., 127.0.0.1, 192.168.x.x, 10.x.x.x) or unexpected external domains that were not initiated by legitimate users
If Haivision Aviwest Manager or Streamhub is installed and exposed on the network, the system is affected by this vulnerability since all versions are vulnerable to unauthenticated SSRF attacks.
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 dataApply available patches from Haivision immediately. Implement network segmentation to restrict server outbound access, configure web application firewalls to filter malicious URL patterns, and disable unnecessary URL-fetching functionality until patched.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1965 — 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-2024-1965 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