/ 
Yote-0.208
/ Yote
Security Advisories (9)
CVE-2020-11022 (2020-04-29)

In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.

CVE-2020-11023 (2020-04-29)

In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.

CVE-2019-11358 (2019-04-20)

jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.

CVE-2015-9251 (2018-01-18)

jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.

CVE-2011-4969 (2013-03-08)

Cross-site scripting (XSS) vulnerability in jQuery before 1.6.3, when using location.hash to select elements, allows remote attackers to inject arbitrary web script or HTML via a crafted tag.

CVE-2012-6708 (2018-01-18)

jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.

CVE-2020-7656 (2020-05-19)

jquery prior to 1.9.0 allows Cross-site Scripting attacks via the load method. The load method fails to recognize and remove "<script>" HTML tags that contain a whitespace character, i.e: "</script >", which results in the enclosed script logic to be executed.

CVE-2019-5428

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

CVE-2014-6071 (2018-01-16)

jQuery 1.4.2 allows remote attackers to conduct cross-site scripting (XSS) attacks via vectors related to use of the text method inside after.

NAME

Yote - Code server side, use client side.

SYNOPSIS

$ yote_server start

Yote is a platform that

* serves up any number of separate applications

* provides account management

* provides access control for objects and methods

Yote on the server side is a server that is a

* container objects exist in a graph structure

* multi-threaded request handling

* Object fields and connections are contents are free form and require no schema definition

Yote on the client is a javascript library that provides

* RPC bound yote objects

* web controls that bind to the yote objects

* web controls for account management

* web widgets for use with yote objects

DESCRIPTION

The purpose of Yote to be able to develop rapidly, flexbily and fluidly. Yote stores a graph of interconnected container objects. Each of these can be connected to any other, and each may have properties attached to them. No schema is needed to describe how objects are connected or what properties they contain.

There is an organization to this object graph, however; all objects that are 'live' can trace back to the root of the graph. This root contains a collection of user logins and application objects. It provides methods for creating these login objects, which, since they are Yote objects, can have arbitrary properties attached to them. The application objects are singleton Yote objects are are accessed via the fetch_app_by_class method attached to the root.

I wrote Yote because I wanted to write object oriented applications, particulally web applications and prototypes, in a ferenic ADHD style. I did want want to have to set up schemas, and then make changes to them as the application changed.

PUBLIC METHODS

get_args

Calling this returns an array ref of configuration arguments as that have been passed in through the @ARGV array or that are saved in the yote configuration. If no configuration has been saved, this program prompts the user for configuration values and saves them if able.

run( %args )

This method activates starts the Yote server with configuration values that have been passed in. It does not return until the yote server has shut down.

BUGS

There are likely bugs to be discovered. This is alpha software.

METHODS

fetch_root()

Returns the Yote Root singleton. Used for some tests.

AUTHOR

Eric Wolf coyocanid@gmail.com http://madyote.com

LICENSE AND COPYRIGHT

Copyright (C) 2011 Eric Wolf

This module is free software; it can be used under the same terms as perl itself.