Skip to content
Fencer Intel
medium 5.3

CVE-2015-3207 json

Insecure cookies in Openshift Origin

published 2022-07-07 4 y ago modified 2026-06-17 4 mo ago also GHSA-rqph-25q9-9jhp , GO-2022-0505 , EUVD-2022-6413

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

In Openshift Origin 3 the cookies being set in console have no 'secure', 'HttpOnly' attributes.

Patch / fix

  • go github.com/openshift/origin 1.0.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-3207 updated cvss 5.3

github.com/openshift/origin: Insecure cookies in Openshift Origin in github.com/openshift/origin

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/elasticsearch6-rhel8, openshift-logging/logging-curator5-rhel8 Red Hat OpenShift Container Platform 4 openshift4/ose-tests Red Hat OpenShift Virtualization 4 container-native-virtualization/cluster-network-addons-operator, container-native-virtualization/cluster-network-addons-operator-rhel9 Red Hat OpenStack Platform 16.2 osp-director-provisioner-container
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/openshift/origin
<1.0.0
1.0.0

Affected products

  • n/a Openshift Origin

Classification

Weakness
  • CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
  • CWE-311 Missing Encryption of Sensitive Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.