Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
The current state of JComponentHelper
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
klas berlič  
View profile  
 More options Sep 1 2012, 5:24 pm
From: klas berlič <klas.ber...@gmail.com>
Date: Sat, 1 Sep 2012 23:18:41 +0200
Local: Sat, Sep 1 2012 5:18 pm
Subject: The current state of JComponentHelper

My 5 cents on JComponent helper returning wrong results:

I originally sent this report to the JSST on 26.7.11, never got any reply
about its content, just standard thank you note. Sent it to JSST as wrong
output of this function combined with vulnerable extension could be a
potential danger - but after more than one year I think it is safe to claim
they decided it is not an issue so I presume my findings are safe to
publish.

====================================================

[image: Slika v vrstici 1]

Clarification for the result column:

   - OK - component renders,
   - NOT_FOUND - system returns COMPONENT NOT FOUND status
   - Marked by red fields are results when under specified conditions
   component renders  when it should indeed return NOT_FOUND.
   - Orange marks conditions when issue is a functional bug, but IMHO not a
   security problem.

Such wrong behavior of  JComponentHelper in my opinion becomes a security
issue if someone relies on Disable to prevent unsafe users from accessing
vulnerable component (backend - second red OK) or when vulnerable component
is deinstalled from a database (== not installed) but files remain there
(e.g. due to file permission problems) - this is valid from the frontend
and marked as first red OK n the results.

Not exactly a release triggering issue, but surely a bug that should be
fixed.

Regards,
Klas

  joomla-component-helper-logic.png
20K Download

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic