yahoo-eng-team team mailing list archive

[Lin Hua Cheng <1447678@xxxxxxxxxxxxxxxxxx>]

** Changed in: horizon
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1447678

Title:
  session ID does not respect the principle of Same Origin Policy

Status in OpenStack Dashboard (Horizon):
  Won't Fix
Status in OpenStack Security Advisories:
  Won't Fix

Bug description:
  This issue is being treated as a potential security risk under
  embargo. Please do not make any public mention of embargoed (private)
  security vulnerabilities before their coordinated publication by the
  OpenStack Vulnerability Management Team in the form of an official
  OpenStack Security Advisory. This includes discussion of the bug or
  associated fixes in public forums such as mailing lists, code review
  systems and bug trackers. Please also avoid private disclosure to
  other individuals not already approved for access to this information,
  and provide this same reminder to those who are made aware of the
  issue prior to publication. All discussion should remain confined to
  this private bug report, and any proposed fixes should be added as to
  the bug as attachments.

  Reported via private E-mail from Anass ANNOUR:

  For the services Horizon, the session ID does [editor's note: did you
  mean "does not" here?] respect the principle of (SOP: Same Origin
  Policy), any one who can open a port in the Horizon server ( > 1024)
  with less privilege can get the session ID of the victim which he had
  convince him/her to visit the port, then the attacker can replay the
  session ID.

  The screenshot vuln2 present the session id catched in a port 9999,
  after i convinced an authenticated victim (tester) that the service is
  faster on port 9999.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1447678/+subscriptions