Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Intended 20 May 2014

uPortal 4.0.13.1 Announcement

Apereo has released uPortal 4.0.13.1, which is uPortal 4.0.13 with security fixes to properly enforce MANAGE and CONFIG permissions.

Prior to this release, portlet administration permissions are bugged such that

  1. CVE-2014-3146 anyone who can SUBSCRIBE the portlet-admin portlet can MANAGE any portlet, regardless of intended delegated administration MANAGE and MANAGE-* permission restrictions , and
  2. CVE-2014-3147 anyone who can SUBSCRIBE a given portlet can enter CONFIG mode of that portlet to the extent that the portlet has a CONFIG mode.



Updating from 4.0.0-4.0.5

If you have data you care about in the UP_LOGIN_EVENT_AGGREGATE table please back it up externally or rename the table before executing the following steps. db-update will drop this table.

After configuring your uPortal 4.0.13.1 source run:

  • ant db-update

Downloads: TODO: have a download link
Release Notes: https://wiki.jasig.org/display/UPC/4.0.13.1
Maven Project Site: http://developer.jasig.org/projects/uportal/4.0.13.1/

Full Release Notes

Release Notes - uPortal - Version 4.0.13.1

TODO: full release notes

-Release Engineer (TODO: credit release engineer)

Issues addressed in uPortal 4.0.13.1

key summary type priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Bugs known to afflict uPortal 4.0.13.1

(Note that this listing is only as good as JIRA issue metadata about affects-version.)

key summary type updated priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels