Vulnerabilities

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Talya Informatics Travel APPS allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Travel APPS: before v17.0.68.

A vulnerability, which was classified as critical, was found in itsourcecode Tailoring Management System 1.0. This affects an unknown part of the file customeradd.php. The manipulation of the argument fullname/address/phonenumber/sex/email/city/comment leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-269805 was assigned to this vulnerability.

A vulnerability has been found in itsourcecode Online Food Ordering System up to 1.0 and classified as critical. This vulnerability affects unknown code of the file /addproduct.php. The manipulation of the argument photo leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-269806 is the identifier assigned to this vulnerability.

A vulnerability, which was classified as critical, has been found in itsourcecode Pool of Bethesda Online Reservation System 1.0. Affected by this issue is some unknown functionality of the file controller.php. The manipulation of the argument rmtype_id leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269804.

Rejected reason: This CVE is a duplicate of CVE-2024-38374.

Authorization Bypass Through User-Controlled Key vulnerability in Talya Informatics Travel APPS allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Travel APPS: before v17.0.68.

A vulnerability classified as problematic was found in LabVantage LIMS 2017. Affected by this vulnerability is an unknown functionality of the file /labvantage/rc?command=file&file=WEB-OPAL/pagetypes/bulletins/sendbulletin.jsp of the component POST Request Handler. The manipulation of the argument bulletinbody leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269803.

A vulnerability was found in LabVantage LIMS 2017. It has been rated as problematic. This issue affects some unknown processing of the file /labvantage/rc?command=page of the component POST Request Handler. The manipulation of the argument param1 leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-269801 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability classified as problematic has been found in LabVantage LIMS 2017. Affected is an unknown function of the file /labvantage/rc?command=page&sdcid=LV_ReagentLot of the component POST Request Handler. The manipulation of the argument mode leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-269802 is the identifier assigned to this vulnerability.

A vulnerability was found in LabVantage LIMS 2017. It has been declared as problematic. This vulnerability affects unknown code of the file /labvantage/rc?command=file&file=WEB-CORE/elements/files/filesembedded.jsp of the component POST Request Handler. The manipulation of the argument sdcid/keyid1/keyid2/keyid3 leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269800. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

The Portfolio Gallery – Image Gallery Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'PFG' shortcode in all versions up to, and including, 1.6.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an<br /> empty supported client protocols buffer may cause a crash or memory contents to<br /> be sent to the peer.<br /> <br /> Impact summary: A buffer overread can have a range of potential consequences<br /> such as unexpected application beahviour or a crash. In particular this issue<br /> could result in up to 255 bytes of arbitrary private data from memory being sent<br /> to the peer leading to a loss of confidentiality. However, only applications<br /> that directly call the SSL_select_next_proto function with a 0 length list of<br /> supported client protocols are affected by this issue. This would normally never<br /> be a valid scenario and is typically not under attacker control but may occur by<br /> accident in the case of a configuration or programming error in the calling<br /> application.<br /> <br /> The OpenSSL API function SSL_select_next_proto is typically used by TLS<br /> applications that support ALPN (Application Layer Protocol Negotiation) or NPN<br /> (Next Protocol Negotiation). NPN is older, was never standardised and<br /> is deprecated in favour of ALPN. We believe that ALPN is significantly more<br /> widely deployed than NPN. The SSL_select_next_proto function accepts a list of<br /> protocols from the server and a list of protocols from the client and returns<br /> the first protocol that appears in the server list that also appears in the<br /> client list. In the case of no overlap between the two lists it returns the<br /> first item in the client list. In either case it will signal whether an overlap<br /> between the two lists was found. In the case where SSL_select_next_proto is<br /> called with a zero length client list it fails to notice this condition and<br /> returns the memory immediately following the client list pointer (and reports<br /> that there was no overlap in the lists).<br /> <br /> This function is typically called from a server side application callback for<br /> ALPN or a client side application callback for NPN. In the case of ALPN the list<br /> of protocols supplied by the client is guaranteed by libssl to never be zero in<br /> length. The list of server protocols comes from the application and should never<br /> normally be expected to be of zero length. In this case if the<br /> SSL_select_next_proto function has been called as expected (with the list<br /> supplied by the client passed in the client/client_len parameters), then the<br /> application will not be vulnerable to this issue. If the application has<br /> accidentally been configured with a zero length server list, and has<br /> accidentally passed that zero length server list in the client/client_len<br /> parameters, and has additionally failed to correctly handle a "no overlap"<br /> response (which would normally result in a handshake failure in ALPN) then it<br /> will be vulnerable to this problem.<br /> <br /> In the case of NPN, the protocol permits the client to opportunistically select<br /> a protocol when there is no overlap. OpenSSL returns the first client protocol<br /> in the no overlap case in support of this. The list of client protocols comes<br /> from the application and should never normally be expected to be of zero length.<br /> However if the SSL_select_next_proto function is accidentally called with a<br /> client_len of 0 then an invalid memory pointer will be returned instead. If the<br /> application uses this output as the opportunistic protocol then the loss of<br /> confidentiality will occur.<br /> <br /> This issue has been assessed as Low severity because applications are most<br /> likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not<br /> widely used. It also requires an application configuration or programming error.<br /> Finally, this issue would not typically be under attacker control making active<br /> exploitation unlikely.<br /> <br /> The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.<br /> <br /> Due to the low severity of this issue we are not issuing new releases of<br /> OpenSSL at this time. The fix will be included in the next releases when they<br /> become available.