Skip to content
Noroxi
CVE-2014-6187· NVD / CVE Program· CNA ibm

Multiple cross-site request forgery (CSRF) vulnerabilities in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x before 6.3.0.5, 7.0

Multiple cross-site request forgery (CSRF) vulnerabilities in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x before 6.3.0.5, 7.0.x before 7.0.0.5, 7.5.x before 7.5.0.3, and 8.0.x before 8.0.0.2 allow remote authenticated users to hijack the authentication of unspecified victims via unknown vectors.

MediumCVSS 6.0 · v2.0—No exploit No fix recorded
Published
Dec 24, 2014
Updated
Jun 16, 2026
EPSS
0.9% · 57th 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

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.9%

Affected systems

VendorProduct
ibmwebsphere service registry and repository

Affected versions

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

  • ibm websphere service registry and repository6.3.0
  • ibm websphere service registry and repository6.3.0.1
  • ibm websphere service registry and repository6.3.0.2
  • ibm websphere service registry and repository6.3.0.3
  • ibm websphere service registry and repository6.3.0.4
  • ibm websphere service registry and repository7.0.0
  • ibm websphere service registry and repository7.0.0.1
  • ibm websphere service registry and repository7.0.0.2
  • ibm websphere service registry and repository7.0.0.3
  • ibm websphere service registry and repository7.0.0.4
  • ibm websphere service registry and repository7.5.0.0
  • ibm websphere service registry and repository7.5.0.1
  • ibm websphere service registry and repository7.5.0.2
  • ibm websphere service registry and repository8.0
  • ibm websphere service registry and repository8.0.0.1

Same product

ibm: all records

Other highest-scoring records for the same primary product.

  • CVE-2009-2750IBM WebSphere Service Registry and Repository (WSRR) 6.3.0 before FP2 does not have the intended configuration properties, which allows remo
    22Monitor
  • CVE-2019-4537IBM WebSphere Service Registry and Repository 8.5 could allow a user to obtain sensitive version information that could be used in further a
    21Monitor
  • CVE-2010-2644IBM WebSphere Service Registry and Repository (WSRR) 7.0.0 before FP1 does not properly implement access control, which allows remote attack
    20Monitor
  • CVE-2014-6179Cross-site scripting (XSS) vulnerability in the Web UI in IBM WebSphere Service Registry and Repository (WSRR) 7.5.x before 7.5.0.4 and 8.0.
    18Monitor
  • CVE-2014-6153The Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.
    18Monitor
  • CVE-2014-6186IBM WebSphere Service Registry and Repository (WSRR) 6.3.x before 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x before 7.5.0.3, and 8.0.x before 8.0
    17Monitor

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.

Credits

All researchers

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

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    P · data or configuration can be modified
    Availability
    P · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    P
    Availability impact
    P

    Weakness class (CWE)

    CWE-352 · Cross-Site Request Forgery (CSRF)

    CVSS vector

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

    nvd-primary

    Root cause

    State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.

    The bug in code

    The whole CWE-352 class

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

    Vulnerable

    ts
    app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);

    Fixed

    ts
    app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    ATT&CK techniques

    —

    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

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records