Skip to content
Noroxi
CVE-2014-8024· NVD / CVE Program· CNA cisco

The API in the Guest Server in Cisco Jabber, when the HTML5 CORS feature is used, allows remote attackers to obtain sensitive information by

The API in the Guest Server in Cisco Jabber, when the HTML5 CORS feature is used, allows remote attackers to obtain sensitive information by sniffing the network during an HTTP (1) GET or (2) POST request, aka Bug ID CSCus19789.

MediumCVSS 4.3 · v2.0—No exploit No fix recorded
Published
Dec 22, 2014
Updated
Jun 16, 2026
EPSS
1.8% · 78th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

Affected systems

VendorProduct
ciscojabber guest

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • cisco jabber guestall versions

Other highest-scoring records for the same primary product.

  • CVE-2016-9224A vulnerability in the Cisco Jabber Guest Server could allow an unauthenticated, remote attacker to initiate connections to arbitrary hosts.
    26Monitor
  • CVE-2020-3136Cisco Jabber Guest Cross-Site Scripting Vulnerability
    24Monitor
  • CVE-2017-6762A vulnerability in the web-based management interface of Cisco Jabber Guest Server 10.6(9), 11.0(0), and 11.0(1) could allow an unauthentica
    24Monitor
  • CVE-2016-1311Cross-site scripting (XSS) vulnerability in the management interface in Cisco Jabber Guest Server 10.6(8) allows remote attackers to inject
    24Monitor
  • CVE-2014-8026Cross-site scripting (XSS) vulnerability in the Guest Server in Cisco Jabber allows remote attackers to inject arbitrary web script or HTML
    18Monitor
  • CVE-2014-8025The API in the Guest Server in Cisco Jabber, when HTML5 is used, allows remote attackers to obtain sensitive information by sniffing the net
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    none
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    None
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:P/I:N/A:N

    nvd-primary

    Root cause

    The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    json
    {  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

    Fixed

    json
    {  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

    References

    All records