Tuesday, March 31, 2009

My Puppy We Is Like Water

3M Tilloy: Elections EC and DP final straight

That we are the elections of staff representatives and EC DP be held on j HURSDAY April 2, 2009 's website Tilloy .

We are in the final straight and Electrics Voters the last words you belong, so be good CHOICE.

The CFDT this on your site Tilloy a dynamic team, which will be effective at your disposal and will defend your rights and your ideas.

We do not hide our ambition and goal to win a maximum of votes and seats in order to confirm our representative on the site but also overall company.

Contrary to popular belief the team CFDT in place, daily gaining staff confidence and steadily increasing the number of members and is is strengthening its legitimacy

We CFDT have a code of ethics and we will respect it, during the elections we will be satisfied (not to say anything) but do not go after people instead.

Awareness is not won by critics and attacks rock (I do not quote anyone)
but through concrete actions each day

Then you colleagues Tilloy you want relevant information, a Support effective and timely communication and integrates so stay in contact with your site:


CFDT VOTE - VOTE CFDT - CFDT VOTE - VOTE CFDT

CFDT-3m @ laposte . net

How To Unlock Sap2102

3M: unlocking your participation in 2009

Regarding your participation under the 2008 Act of December 4, 2008 (Official Gazette) allow you to unlock (beware subject to taxation) However

3M is awaiting Official publication of the decree (this should not be long now), to the social partners sign an agreement authorizing the release.

All this seems complicated, however, you should receive within a few days your newsletter AXA on which you should see a checkbox (immediate release).

Stay in contact with your blog to keep record participation

cfdt-3m@laposte.net

Thursday, March 26, 2009

Royal German Surname Meanings

2008 3M HEALTH : Stopping stages but it is late and there blocking

The CFDT takes over from the FP blog 3M Health to disseminate the maximum Information about events and a major objective to support them in their actions.

At that time (23h) stop talks too much difference between the proposals of social partners and the leadership ... Resuming
tomorrow.


(image taken from the emission channel + 25 March "the horns"

find the horns on Canal + dated March 25, 2009 (VIDEO)
http://player . canalplus.fr /? CPDM69GJv5kCFVWK3godaTobfQ gclid = # / 226937

cfdt-3m@laposte.net

My Puppy Wee Is Like Water

3M HEALTH: negotiations

At 8:57 p.m. the negotiations are still underway between management and the social partners.
points of blockage persists and it seems that management is not inclined to will make concessions (as of Hab), the mobility would leave one measure that would block (although one must be careful because it is difficult to get info because elected officials are very very taken)

The CFDT support the claims widely social partners because it is still difficult to accept such a mess when one sees profits Pharaonic fact that the 3M group.

A delegation inter-union of elected CERGY should be on this site Pithiviers Friday, March 27 in late morning to support the all staff and elected (FOR, CFE-CGC and L3MS)

cfdt-3m@laposte.net

Wednesday, March 25, 2009

Wear Socks At Pilates

3M HEALTH: Luc Rousselet still sequestered

Communication on the extent of the conflict beyond the region Pithiviers, information is now taken up by the national media, here enclosed an article online LCI's website this morning on the television channel at 8 a report of 2 minutes in which we see Luc Rousselet speaking and social partners.

Article
http://tf1.lci.fr/infos/economie/social/0, ,4314980,00-the-director-of-3m-receiver-in-the-factory.
html
cfdt-3m@laposte.net

Tuesday, March 24, 2009

Damask Green And Silver Wrapping Paper

3M HEALTH: there is fire in Pithiviers

ago Pithiviers on fire and it thickens from today

The director of 3M Pithiviers sequestered by employees

Since Tuesday afternoon, employees of Site pharmaceutical 3M Pithiviers (Loiret ) kidnap their manager. They oppose the redundancy plan that provides 110 jobs for the removal of the 235 remaining and conditions accompanying the dismissals. Employees, on strike since March 20, require renegotiation severance, leave a mobility period of 24 months, a transfer bonus and guarantees for the remaining employees. "If 3M wants to reorganize, it will that it pays! , "warns Jean-François Caparros, the Workers Force union delegate.

Stock price minutes
20:30 on sub-prefect is present on the site and the strikers are awaiting the arrival of the police
.........
director Luc ROUSSELET is still sequestered


attached following article (source)
http://www.libeorleans.fr/libe/2009/03/le-directeur- de.html

Enclosed please find the video of EN 3 center (blog CFE-CGC )
http://blog-cfe-cgc-3m-sante- pithiviers.over-blog.com/pages/Passage_a_FR3_Centre_Decembre_08-953618.html

The CFDT confirms its solidarity with and support the actions of social partners Pithiviers site.

It is unfortunate that happened but every time the same thing the management does not want to negotiate minimum out what has the means to do things decently because we must not forget that Case is always the employee side, he looks at the shareholder's equity portfolio grow and grow at will.

not forget also the distribution of stock options for $ 11 million (thank you, gentlemen of the Board in the U.S.) and members of our executive stock option France how have they affected

cfdt-3m@laposte.net

Sunday, March 22, 2009

What Not To Have In A Kitchen Worksheet

[STANDARD] OWASP - Episode 10




We're Here! The last step with the end of our adventure on the methodology OWASP. After seeing a large number of checkpoints - gathering information for the operation of injections - it remains for us to see the possible attacks on AJAX. I shall conclude with a quick summary on the vision of the standard for the "post-pentest.



Tenth episode! Yep, here we go! It summarizes the section 4.11 of the standard. I will go very quickly because I am not an expert
AJAX;) But I had to be comprehensive in addressing all the chapters of the methodology. Finally, I will describe briefly in Part 5 of OWASP regarding the work of a PenTest once the tests.

2 -
active testing phase 9 -
testing AJAX applications


AJ-001 - AJAX Vulnerabilities

Our approach is a first step in exploring the potential vulnerabilities in AJAX applications or at least check that there is no flaw exploited by an attacker. To ensure this, we must cover a broad field of research because AJAX apps are affected by many attack vectors: The injection attacks (see episode 7): ex; SQL / XSS / CSRF; denial of service (see episode 8); Attack on the client side (browser). Monitoring new vulnerabilities! (Eg www.securityfocus.com ).


AJ-002 - Testing AJAX applications

There is no accurate method but here we give some hints. The first is to work with a local proxy (eg
paros
    ). As with any type of web application, this kind of tool we can often find "what's wrong." At least it allows us to better understand the application.
  • The second track is to find the errors or deficiencies in the JavaScript code. This time, we can use a Firefox extension like Firebug
  • . The goal is to find loopholes in the code that will allow us to make shots.
  • 3 - After the tests ...

The achievement tests form the core of the provision of a penetration test of a web application. However, the end result is the report.

3.1 - Study of vulnerability
However, the end result is the report. OWASP provides six steps to investigate a fault:

Step 1: Description and identification of risk flaw found
For example, damage to company image, financial loss, etc. ...

Step 2: Estimating the probability


Is it conceivable that Such an attack will occur? If yes, how? For example, if there is financial gain to the key, an attacker will be more motivated to attack the target in question. Second case: imagine a remote attack. If the company has secured external access with properly configured firewall and web protection platform, the attack will be less chance of success.

Step 3: Estimating the impact on the company

Identified risks should be assessed. We bring a different coefficient depending on whether one or more persons may be affected by the operation of the fault study. The financial impact do they consist of a one-day loss of production or of a longer duration?

Step 4: Estimate the severity of risk.


severity risk = probability of achievement (step 2) * Impact (step 3)
We get a criticality "Low" to "Critical".


Step 5: Recommendations

It is time here to provide solutions to correct the faults. The recommendations should take into account the context of the client so they can be realized.


Step 6: Customizing
The idea here is to refine the study by providing a personalized view for the customer solutions tailored to industry, and the changing needs of the business.
3.2 - Report Writing


We cut the ratio by three points:
part for managers (with a summary of tests);

some technical operational teams;
achieving the actual tests taking into account the work done in 3.1.



Conclusion / Briefly

To conclude ten posts about the methodology OWAP, I would say it is for me the only proven standard
    dedicated to Web applications. It has the advantage of treating all types of
  • most common tests (eg injections) and testing of new attractions WEB technologies (eg AJAX application). Second, it addresses all these issues in a very technical way
  • (Part 4 of the document) but also the surrounding parts to offer a full penetration test (context
  • tests, evaluating results, writing a report
  • ).
short, a very interesting thread for those who want to conduct a test Intrusion WEB application rigorously.

Thursday, March 19, 2009

Kitchens Deorated With Apples

[STANDARD] OWASP - Episode 9


A big step, we come to the end of our study methodology OWASP. In this ninth episode, we discuss Web Services. Casually, it's crazy what they can afford to do! But as always, everything depends on the security of their implementation. So, ready to test?


1 - Foreword
OWASP In the standard, this Section 4.10. Appointed Web Services Testing - WAS
, it addresses the main lines of attack of the services in their discovery to their use in seven points.

2 -
active testing phase 8 -
tests on Web Services


2.1 - Collection of information on Web Services

If we do not know the location Web Services on the Web server host and that it is not trivial, we will find it. For this, several means available to us: thanks to our friend Google with a query like: inurl: wsdl site:
target_name


through sites such as censuses Web Services
seekda.com
,
Alternatively we can try to find them with the roads, well known names and extensions to it, take the known URLs and add (combine):
/ services / service_name

  • wsdl, uddi , disco, etc.. Try also by preceding them with a "?"


2.2 - Testing WSDL
  • the WSDLs Once identified, we will have access to their description. This interest to us then, what are the names
  • operations (possibly with their parameters); URLs and / or IP addresses provided (external or internal addresses ...). For this, two tools can be used: WebScarab
  • (full version) and
WSDigger
.


2.3 - Structure of XML files
  • description of WSDL is saved in XML format. This paragraph focuses on the proper formation of these XML files. For this, we will check the following:
file is properly formed? The tags are they properly closed?
elements they can inject large data? elements they can inject binary (possibly in base64)?
elements adequate to launch malicious injections (see Episode 8)?



2.4 - XML Content-Level Attack

    Following the analysis in the previous step, we will try to exploit potential vulnerabilities identified. The goal is to have fun with the settings and turn them to our way to test the behavior of the server and / or carry out attacks. This assumes, however, can interact with the WSDL.
  • We will illustrate this with the following screenshot (with WebScarab):
  • To begin, we choose the WSDL that we want to test (
  • WSDL:
). Then we choose the operation that interests us (1). Then, we change the parameter value desired (2). We instruct the tool to create the SOAP request associated simply by clicking on "Execute

" (3). The result is given in (4).

2.5 - HTTP Request GET


This time we try to change settings directly via the URL. indirectly, our goal is to act on the WSDL. Then, within the parameters, we will modify the values supplied in GET requests, or better, execute commands preceded by the appropriate separator (eg
& '; or SOAP WSDL also destined for the target with the difference that we seek to incorporate an attachment in the application. The objective is - for example - to upload to the Web server program that allows us to take over. As suggested by the methodology, the test may be a EICAR test.
2.7 - Replay Attack
We work both locally and this after launching a MITM attack. So our goal is to recover the valid elements of a session (credentials, cookies, etc. ...) in order to appropriate the past queries by other users in the replay. We will require tools to sniff the traffic (eg wireshark

) + tcpreplay
and / or WebScarab.

Wednesday, March 18, 2009

Clever Wording Response Wedding

[STANDARD] OWASP - Episode 8



We continue our momentum to address the eighth episode of the methodology OWASP. This is to handle DoS attacks. Seldom asked in a pentest, yet pests effects on success ...




1 - Foreword



This section corresponds to section 4.9 of the standard, named
Denial of Service Testing - DS
. Speaking of denial of service attacks and the corresponding should only be undertaken if they are explicitly requested. Indeed, the company claims is rarely prepared to take the risk of its falling prod '. However, testing can be conducted on a test environment or the client may very well be interested in extensive testing or denial of services largely for them.
active testing phase 7 -
tests dDoS


2.1 - DS-001: DoS attack based on "wildcard characters"

The wildcard characters "are characters special replace multiple characters or strings. For example, the character "*" can replace all the strings. The goal is to use them to force the target database to search as long as possible to respond to our request. Here are some rules to follow:

The application must request an absent or very rare in a very wide field of research;
Use long and complex queries with wildcard characters ";
Begin and end the application by a "%" (for
LIKE
).

The purpose of this attack and make the DB unusable or at least very slow.
2.2 - DS-002: Block user accounts Generally, a threshold is imposed on the number of attempts allowed to connect with an account. This prevents such attacks by brute force. " However, once all the tests exhausted, the account is blocked for a period indétermminée. We have two cases:
We know the login accounts to be blocked. In this case, try at least 15 trials to block the account;
We know of no login. So we must find grace:
messages and pages error provided from the login page (point already treated);
page creation account in trying to create a user already exists;
page to recover your password (point already Treaty).
  • 2.3 - DS-003: DoS attacks based on type "Buffer Overflow"
  • We have already discussed the issue of buffer overflow in the previous episode. The difference is that here the goal is simply inaccessible to a service. For example, we can check if a page or feature is no longer available due to our attack.
  • 2.4 - DS-004: DoS on object allocation

Among the actions allowed for the user, it can sometimes - directly or otherwise - create instances of any object (property, characteristic , entered into a database, etc.).. For illustration, in code, creating an object will be a new

.

2.5 - DS-005: Using a loop
  • coders often use loops in their programs. If a loop is located or suspected, the user may attempt to exceed the limits of a loop (eg in the case of a loop for
  • ) or start an infinite loop (eg a while loop
    • ).
    • 2.6 - DS-006: Saturation of a disk
    If the log management is not secure, it may happen that many logs are recorded. Also, it is possible that the disk hosting the logs did not have enough space. So, the goal of the attacker will generate a maximum set of logs to use the system log. This attack will usually using automated scripts or queries consuming disk space.

2.7 - DS-007: Saturation resources

resources created on ask the server for other resources (disk, CPU, RAM, and / or network). If they are not closed properly or reallocated, they accumulate and can cause an overload of some kind. For example, we have:

files that are not properly secured locks;
accumulated resources which require RAM too large for the server's capabilities; connections still active until it reaches a BDD threshold allowed (ex: 15 simultaneous connections).


2.8 - DS-008: Saturation of a session
Here, we try to store much data in one session. Also, it can be to create a maximum session to overload the server. Ideally, we will combine the two. Requirements in terms of memory is now increasingly strong for the server that will almost certainly end up not having the capacity to provide such a request.

Thursday, March 12, 2009

Duck Billed Platypus Origami

[STANDARD] OWASP - Episode 7



seventh episode of our saga to the knowledge of the methodology OWASP. We do not yet cover all topics, or even the classics. Indeed, if there is one recipe that works almost every time in terms of PenTest WEB apps, what are the injections of all kinds !





  • 1 - Foreword
  • The episode 7 deals with the control data inputted by a user (
Data Validation Testing - DV
). In the case of an attacker, he will try to inject special characters and malicious code if the data control is not effective. The goal is not to explain how each type of injection (or so I tried the blog page the longest of the canvas) but to review the main options available to an attacker proposed by the standard.


2 -
active testing phase 6 - testing on injections
2.1 - DV-001: non-persistent XSS

There are two types of XSS attack (or Cross Site Scripting) XSS
nonpersistent that are not maintained in the application, launched into "one-shot" (see paragraph present);
persistent XSS that are maintained and can be replayed by victims without their knowledge by consulting a page affected by such forward without intervening again (see next paragraph);
There are actually a third category More specifically, CSRF attacks (seen in episode 4).
Find non-persistent XSS, we address the following approach:

What are the possible entries? Where we have a chance to succeed in such an attack. The answer has usually been elucidated in episode 1; Analysis Phase: XSS attempt a classic (see example below. Encode application if necessary).
phase attack: inject the desired code (eg retrieval of cookies).



2.2 - DV-002: Persistent XSS
  • The persistent XSS are even more popular since the attacker may have an impact after the fact. A similar approach is followed to inject these codes:
  • Find a way to "save" your XSS (form, profile page, configuration page, etc.).
analyze the HTML of the page to find the field vulnerable;
    Test with a classic XSS (another example is provided below).

  • inject code that will run when the infected page is accessed manually or automatically (Eg by a rope). It is also possible to use the tools of exploitation (a future post?).
2.3 - DV-003: DOM Based XSS

In gray box, this test is to
find in the code functions potentially injectable (eg document.location, document.URL ...) ;
attempt the attack:

ex1: # concatenate the character
    tracking malicious code (javascript) in the URL;
  • ex2: try the XSS code in place of the parameter values.
  • I invite you to see the document
Amit Klein for more info on this subject. 2.4 - DV-004: Cross Site Flashing
  • Here we test the safety of flash animations:

First, get the *. swf
with a simple wget

;
  • Then
  • use flare to decompile;
    • Find methods potentially dangerous (eg
    • loadVariables () , getURL ()
    • , etc.).
    • inject malicious code (eg
    javascript: code_malicieux
). To cite only one, there is an audit tool for this kind of animation:
SWFIntruder
.

2.5 - DV-005: SQL injection

    Here, tackling a very large pieces. The standard is the magnitude of the subject by treating the databases the most famous (MySQL, Oracle, MS SQL, Access, PostgreSQL). We broach the principle here that very (very very) large.
  • The successful attack mostly in the field on a form, a search field, a field of e-commerce; Test special characters and strings that can allow us to build SQL queries:
  • '- AND OR / *
  • Launch SQL injections by guessing the underlying queries (eg
  • a gold '1 '= '1
  • ) 2.6 - DV-006: LDAP injections
  • LDAP bases often contain information as sensitive as those we could have recovered in vulnerable databases (see previous paragraph). Concretely, the attacks will generally be realized as follows: use the character *
instead of legitimate values to view all results; try characters ( for authentication, there are more complex attacks (example below).

username => *) (uid =* uid =*))( injection attacks are similar to those already mentioned in DV-005;
if test mode box gray / white, to study the code that will certainly reveal new vulnerabilities.


    2.8 - DV-008: XML injections
  • XML is now widely used to transport information between the GUI and the database. It is common to have this format in a pentest. A new track for the audit!
  • Test special characters accepted and might contribute to an injection:
  • " &

Knowing the structure of the database. Is it possible to read the DTD? If yes, identify the field names of interest ... Use the type Entity with the & character;
Test by inserting a tag injection of malicious tags in the field vulnerable.

As an example, we take a field that adds a user in the database. We'll add two of the following:
second example we add an additional property to our user:



2.9 - DV-009: ISS injections

SSI "Server Side Includes "provides dynamic code in its HTML pages. Which pages are vulnerable? In general, pages with the extension *. shtml but not necessarily. So how to know Again, test the reaction server address special characters:

  • Then ... Out! Here's an example below:

2.10 - DV-010: XPATH injection
XPATH is the language that used to interpret XML files. The attacks will be very similar to an SQL injection:

    How to test? Trying character
  • ' . This causes there an error interesting? < > Test a classic SQL injection (DV-005 for examples rather than classical) Adapting the attack if it becomes aware of the associated XML.
  • the same way as SQL, we can attempt an attack blindly.

2.11 - DV-011: Injection IMAP / SMTP
Well, it is not necessary to present the IMAP and SMTP, but do you know the possible attacks on these protocols in terms of injection?

Injection in the URL: modify a parameter giving a zero value, or containing a random character special. You can also change the name of the parameter or change it altogether. Through these tests, you will know better the behavior of the mail server. Complete your knowledge generating errors on the parameters and values vulnerable after the first point. The goal is to understand the flow structures and interesting email. Test injections without being connected (eg using the IMAP commands) and then the being if you have an account (eg use the CRLF at the right place in the mail that is not constituted as the body message ...).

2.12 - DV-012: Injection code < ! # = / . " - > In the URL, it is sometimes possible to run commands by changing the settings with malicious code (encoded). In gray box, we will look for pieces of code or function that allows input of code and, more importantly, accepts injections to code execution on the host server (eg a simple

ls).
2.13 - DV-013: OS Commanding
Interacting with the server host is a big step in our attack phase. The most traditional methods are to chain malicious carry instructions to lawful instructions. In general, this amounts adding:


&
    followed by the command (Windows);
  • ;
  • followed by the command (Linux)
  • ;
  • marker byte is where you can inject an address that redirects to our malicious code;
In the case of an attack
string, use the following strings:
% x,% s
and % n attempt to corrupt the application.
  • 2.15 - DV-015: Vulnerability Incubating
  • This time we are trying to corrupt the application to "applicant" malicious code that we can reuse it for our pousuivre attack (for example, a backdoor) or hoping a nice victim drives our trap.

It may be simply upload our code with a nice field (eg field for file upload);
Also, it can be XSS, SQL Injection + XSS ... (Eg in a forum);
Or, taking advantage of a security breach or configuration. For example, one can inject a malicious WAR file (see the post on Jonas and JBoss

...).

2.16 - DV-016: Splitting and Smuggling attack
  • A splitting attack is to arrange to send two HTTP requests including one in particular which should not normally be accepted by the Web server.
  • Use CRLF with your malicious application. For info, we can encode the CRLF in
  • % d% a ...
  • The entire application must be encoded;
  • To complete the attack, the fields we modifons Last-modified with a date in the future (this field is in the header of the HTTP request).
  • More than words, an example below:
fr% 0D% 0AContent-Length% 3A% 200% 0D% 0A% 0D% 2F1.1% 0AHTTP% 20200% 20OK% 0D% 0AContent-Type% 3A 2Fhtml% 20text%% 0D% 0AConteny-Length% 3A% 2031% 0D% 0A% 3CHTML%% 3ESuccessfully 20Hacked!% 3E% 3C% 2Fhtml


Saturday, March 7, 2009

How To Stop Kidde Smoke Alarm Beeping

GPEC: We were talking about during our meeting in the clubhouse

GPEC THE WHAT IT USED TO:

A law dating 18 January 2005, entered into force on 1 January 2006, requires 3M , like all companies or groups of more than 300 employees, to start negotiations on the three-year terms and information consulting the works council about the company's strategy and its effects on employment (art. L. 320-2 Labour Code).

This law also requires the implementation of a management
of jobs and skills ( GPEC) and elements associated with it:

training, validation of the experience, skills assessment , support for mobility ...

This negotiation should be coupled with those concerning the continued employment of older workers and their access to vocational training.

An prevention by anticipating

This complex, renegotiated every 3 years, allows:

  • to anticipate developments in staffing and skill needs employees in each industry and service to a specific deadline (3 years in most cases), depending on parameters such as advances in technology, business strategy, etc..
  • to implement the provisions necessary in terms of adaptation employee training, career mobility (bridges) and / or geographical priority internally within the enterprise or group concerned.
  • monitor and adapt its provisions permanent

Important issues

But it is not only to negotiate a GPEC because the law requires. 3M is concerned, like any other business, several important issues that will integrate GPEC. The next demographic crisis, for example, needs to plan and organize notes that there are many employees who retire. Mutations are more rapid in all professions: some will decline or be transformed, others develop, new ones may appear.

In this context the ever changing interests of each party must be combined: for the Biosafety employees on their jobs and their requirements in terms of qualification, the company planned the adequacy of staffing needs and competencies, guaranteeing its competitiveness.

If you have questions about the topic we CFDT are at your disposal to answer in the next hotlines that we are hosting, the site of Cergy

cfdt-3m@laposte.net

Friday, March 6, 2009

Rechargeable Fm Transmitter

NAO 2009: last visit March 13, 2009

The final meeting between the social partners and management for NAO 2009 will be held Friday, March 13, 2009 (morning).
The wage freeze is confirmed and we can even talk about a wage freeze, however there is a possibility to receive a bonus that is always set at a height of 400 € paid in June and possibly an additional 200 € disbursed at the beginning September 2009.

We can only encourage management to consider the proposals of social partners and reward staff efforts by giving them a decent premium of at least 1000 € (for memory and recall that premium does is not subject to charges for the employer)
While we look forward to seeing you in the late afternoon of Friday 13 to inform you of the decision of management.

And if management persists and remains strong with its position and though we encourage you to " BOYCOTT THE NEXT MEETING " QUARTERLY CEO " .

cfdt-3m@laposte.net