CN113326539B - Method, device and system for private data leakage detection aiming at applet - Google Patents
Method, device and system for private data leakage detection aiming at applet Download PDFInfo
- Publication number
- CN113326539B CN113326539B CN202110699084.2A CN202110699084A CN113326539B CN 113326539 B CN113326539 B CN 113326539B CN 202110699084 A CN202110699084 A CN 202110699084A CN 113326539 B CN113326539 B CN 113326539B
- Authority
- CN
- China
- Prior art keywords
- detection
- page
- code
- applet
- type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- General Health & Medical Sciences (AREA)
- General Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Human Computer Interaction (AREA)
- Medical Informatics (AREA)
- Databases & Information Systems (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Storage Device Security (AREA)
Abstract
The embodiment of the specification provides a method, a device and a system for private data disclosure detection of an applet. The method is applied to a detection assembly on terminal equipment, the applet is borne by a service platform, the terminal equipment is provided with a client of the service platform, and the method comprises the following steps: in response to receiving a detection task for a first page in the applet, which is issued by a detection server, opening the first page in the client, and injecting a detection code into the first page, wherein the detection code comprises a first code; searching a first type of triggerable control in a first page by using a first code; if the first trigger event is found, executing a first trigger event of the first type of triggerable control in the first page; acquiring first information returned by a background server of the applet aiming at a first trigger event, and a first interface used by the background server for transmitting the first information; and if the first information comprises plaintext privacy data, generating and returning a first detection result for indicating that the privacy data is leaked from the first interface.
Description
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a method, a device and a system for detecting private data leakage of an applet.
Background
An applet is an application that can be used without download and installation. Some existing service platforms (e.g., payment platforms, social platforms, etc.) may host multiple third party applets. When a user uses an applet in a service platform, for example, when the applet is used for the first time, it is usually necessary to authorize some private data of the user stored in the service platform to all parties of the applet. Thus, the applet may have a problem of leakage of private data.
Therefore, a reasonable and reliable scheme for detecting disclosure of private data of various applets carried by the service platform is urgently needed.
Disclosure of Invention
The embodiment of the specification provides a method, a device and a system for detecting privacy data leakage of an applet, and the method, the device and the system can be used for detecting privacy data leakage of various applets loaded by a service platform.
In a first aspect, an embodiment of the present specification provides a method for detecting leakage of private data for an applet, which is applied to a detection component on a terminal device, where the applet is borne by a service platform, and the terminal device is installed with a client of the service platform, and the method includes: in response to receiving a detection task for a first page in an applet, which is issued by a detection server, opening the first page in the client, and injecting a detection code into the first page, wherein the detection code comprises a first code; searching a first type of triggerable control in the first page by using the first code, wherein the first type of triggerable control is used for triggering privacy data authorization by a user of the client; if the first type of triggerable control is found, executing a first trigger event of the first type of triggerable control in the first page; acquiring first information returned by a background server of the applet aiming at the first trigger event, and a first interface used by the background server for transmitting the first information; determining whether the first information includes plaintext privacy data; and if the determination result is yes, generating and returning a first detection result, wherein the first detection result comprises the first interface and is used for indicating that the first interface has private data leakage.
In some embodiments, said injecting detection code in said first page comprises: injecting the detection code in an applet container of the client, thereby causing the detection code to be injected into the first page.
In some embodiments, the detection code further comprises code for a function library comprising a first function for finding the first type of triggerable control; and said finding a first type of triggerable control in said first page using said first code comprises: calling the first function by using the first code to search the first page for the first type of triggerable control.
In some embodiments, the detection code further comprises a second code; and the method further comprises: searching a plurality of page elements in the first page by using the second code; the searching for the first type of triggerable control in the first page by using the first code includes: searching the first type of triggerable control in the plurality of page elements using the first code.
In some embodiments, the detection code further comprises a third code; and the method further comprises: if the first type of triggerable control is not found in the first page, searching a second type of triggerable control in the first page by using the third code; for each found second type of triggerable control, executing a second trigger event of the second type of triggerable control in the first page; obtaining second information obtained by the applet in response to the second trigger event; determining whether the second information includes plaintext privacy data; if the determination result is yes, one of the following items is classified into the second detection result: the mark of the second type of triggerable control and a second interface of the background server for transmitting the second information are arranged; and returning the second detection result.
In some embodiments, the classifying one of the following items into the second detection result specifically includes: if the second information is obtained locally by the applet, the identifier of the second type of triggerable control is classified into the second detection result; and if the second information is acquired by the applet from the background server, classifying the second interface into the second detection result.
In some embodiments, after executing the second trigger event of the second type of triggerable control in the first page, the method further includes: and blocking the calling of the small program to the information display interface of the small program.
In some embodiments, before said returning said second detection result, further comprising: searching plaintext privacy data in the first page by using the third code; if the second detection result is found, the search result information is classified into the second detection result, and the search result information comprises one of the following items: the element identifier of the page element of the found plaintext privacy data in the first page, and the third interface of the background server for providing the found plaintext privacy data.
In some embodiments, the detection code further comprises code for a library of functions, the library of functions comprising a second function for finding the second type of triggerable control, and/or a third function for finding clear private data presented on a page; and when the function library comprises the second function, the searching a second type of triggerable control in the first page by using the third code comprises: calling the second function by utilizing the third code to search the second type of triggerable control in the first page; when the function library includes the third function, the searching for plaintext privacy data in the first page using the third code includes: and calling the third function by utilizing the third code to search plain text privacy data in the first page.
In some embodiments, the method further comprises: and after the detection of the first page is finished, returning a detection completion notification message.
In some embodiments, the detection task is included in a detection task list generated by the detection server for the applet, each detection task in the detection task list includes different pages in multiple pages of the applet, and each detection task is issued to the detection component by the detection server in sequence.
In some embodiments, the detection task is issued by the detection server using a lua script.
In a second aspect, an embodiment of the present specification provides a system for detecting private data leakage for an applet, including a detection server and a detection component, where the applet is borne by a service platform, and the detection component and a client of the service platform are located in the same terminal device; the detection server is configured to acquire a plurality of pages of the applet according to the program identifier of the applet; generating a detection task list aiming at the small program, wherein each detection task comprises different pages in the multiple pages; sequentially issuing the detection tasks to the detection assembly; the detection component is configured to respond to receiving a detection task aiming at a first page in any page of the plurality of pages, open the first page in the client and inject detection codes into the first page, wherein the detection codes comprise first codes; searching a first type of triggerable control in the first page by utilizing the first code, wherein the first type of triggerable control is used for triggering privacy data authorization by a user of the client; if the first type of triggerable control is found, executing a first trigger event of the first type of triggerable control in the first page; acquiring first information returned by a background server of the applet aiming at the first trigger event, and a first interface used by the background server for transmitting the first information; determining whether the first information includes plaintext privacy data; and if the determination result is yes, generating and returning a first detection result, wherein the first detection result comprises the first interface and is used for indicating that the first interface has private data leakage.
In a third aspect, an embodiment of the present specification provides an apparatus for performing privacy data disclosure detection on an applet, where the apparatus is applied to a detection component on a terminal device, the applet is borne by a service platform, and the terminal device is installed with a client of the service platform, and the apparatus includes: the code injection unit is configured to respond to the receiving of a detection task which is issued by a detection server and aims at a first page in an applet, open the first page in the client and inject detection codes into the first page, wherein the detection task comprises first codes; a search unit configured to search the first page for a first type of triggerable control for a user of the client to trigger privacy data authorization using the first code; the event triggering unit is configured to execute a first triggering event of the first type of triggerable control in the first page if the searching unit finds the first type of triggerable control; the acquisition unit is configured to acquire first information returned by a background server of the applet aiming at the first trigger event, and a first interface used by the background server for transmitting the first information; a determination unit configured to determine whether the first information includes plaintext privacy data; and the generating unit is configured to generate and return a first detection result if the determination result of the determining unit is yes, wherein the first detection result comprises the first interface, and is used for indicating that the first interface has private data leakage.
In a fourth aspect, the present specification provides a computer-readable storage medium on which a computer program is stored, wherein when the computer program is executed in a computer, the computer is caused to execute the method described in any implementation manner of the first aspect.
In a fifth aspect, the present specification provides a computing device, including a memory and a processor, where the memory stores executable code, and the processor executes the executable code to implement the method described in any implementation manner of the first aspect.
In a sixth aspect, the present specification provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the method described in any implementation manner of the first aspect.
The embodiments of the present specification provide a method, an apparatus, and a system for detecting private data leakage for an applet, where the method is applied to a detection component, the applet is borne by a service platform, and the detection component and a client of the service platform are located on the same terminal device. For any applet borne by a service platform, a detection task list can be generated for the applet through a detection server according to a plurality of pages of the applet, and each detection task in the list is sequentially issued to a detection component, so that the detection component can open a first page in a client in response to receiving a detection task for any first page in the plurality of pages, inject a detection code including a first code into the first page, then search a first type of triggerable control for user trigger privacy data authorization of the client in the first page by using the first code, then execute a first trigger event of the first type of triggerable control in the first page under the condition that the first type of triggerable control is searched, then acquire first information returned by a background server of the applet for the first trigger event, and the background server is used for transmitting the first information through the first interface, then determining whether the first information comprises plaintext privacy data, and generating and returning a first detection result comprising the first interface when the determination result is yes, wherein the first detection result is used for indicating that the privacy data is leaked from the first interface. Thus, the detection component can be enabled to perform privacy data leakage detection on the first page in a code injection mode. By adopting the detection scheme, the private data leakage detection of various applets borne by the service platform can be realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments disclosed in the present specification, the drawings needed to be used in the description of the embodiments will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments disclosed in the present specification, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
FIG. 1 is an exemplary system architecture diagram to which some embodiments of the present description may be applied;
FIG. 2 is a schematic diagram of one embodiment of a method for private data disclosure detection for applets, according to the present description;
FIG. 3 is a schematic diagram of a task issuing process;
FIG. 4a is a schematic diagram of a first type of triggerable control;
FIG. 4b is another schematic diagram of a first type of triggerable control;
FIG. 5 is a flow diagram of one embodiment of a method for private data disclosure detection for applets, in accordance with the present description;
FIG. 6a is a schematic diagram of a second type of triggerable control;
FIG. 6b is a schematic illustration of the plaintext privacy data found;
FIG. 7 is a schematic diagram of an architecture of a system for private data disclosure detection for applets, according to the present description;
fig. 8 is a schematic configuration diagram of an apparatus for privacy data leakage detection for an applet according to the present specification.
Detailed Description
The present specification will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. The described embodiments are only a subset of the embodiments described herein and not all embodiments described herein. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step are within the scope of the present application.
It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings. The embodiments and features of the embodiments in the present description may be combined with each other without conflict. In addition, the terms "first", "second", "third", and the like in the present specification are used only for information distinction and do not play any limiting role.
As mentioned above, when a user uses an applet in a service platform, for example, when the applet is used for the first time, it is usually necessary to authorize some private data of the user stored in the service platform to all parties of the applet. Thus, the applet may have a problem of leakage of private data.
Based on this, some embodiments of the present specification provide a method for detecting leakage of private data for an applet, by which detection of leakage of private data for various applets carried by a service platform can be achieved. In particular, FIG. 1 illustrates an exemplary system architecture diagram suitable for use with these embodiments.
As shown in fig. 1, an exemplary system architecture suitable for use with these embodiments may include a detection server, a detection component, and a service platform. Wherein, the service platform bears the applet of a third party. Typically, a service platform carries multiple third party applets, i.e., multiple applets. In addition, a service platform typically includes a server and a client. In the client, the page of any applet borne by the service platform can be opened. Note that the page of the applet may be an HTML (HyperText Markup Language) 5 page.
In addition, the service platform may provide various services, which may include, for example, payment services, instant messaging services, social services, financial services, insurance services, and the like, which are not specifically limited herein. When the service platform provides payment services, it may be referred to as a payment platform (such as the payment platform shown in fig. 1). When the service platform provides an instant messaging service, it may be referred to as an instant messaging platform. When the service platform provides social services, it may be referred to as a social platform. When the service platform provides a financing service, it may be referred to as a financing platform. When the service platform provides insurance services, it may be referred to as an insurance platform.
When private data leakage detection needs to be performed on any small program borne by the service platform, the detection component and the client of the service platform can be deployed on the same terminal device. The terminal device may be various electronic devices, and the various electronic devices may include, for example, a smart phone, a tablet computer, a desktop computer, a notebook computer, and the like.
The detection component may be implemented as any form of component on the terminal device, for example, as a software module, client software, or a code file, and is not limited in this respect. In practice, the detection component may control the above-mentioned client installed on the terminal device. Specifically, the detection component may open a page of any one applet hosted by the service platform in the client and perform an operation related to the detection of the leakage of the private data on the page.
The detection server is a server providing support for the detection component. The detection server side can generate a detection task list aiming at any one applet borne by the service platform, wherein each detection task comprises different pages in a plurality of pages of the applet. And then, the detection server side can issue the detection tasks in the detection task list to the detection component, so that the detection component can perform privacy data leakage detection on the page of the applet according to the received detection tasks.
The exemplary system architecture is further described with the service platform as the payment platform.
As shown in fig. 1, the payment platform carries a plurality of applets, such as applets a1, a2, A3. For any one of the applets, for example, the applet a1, when privacy data disclosure detection needs to be performed on the applet a1, the detection server may generate a detection task list for the applet a1, where each detection task includes a different page of multiple pages of the applet a1 (for example, each page of the applet a 1). And then, the detection server side can sequentially issue each detection task in the detection task list to the detection component. It should be noted that the detection server may issue each detection task to the detection component at one time, or issue one detection task of each detection task at a time, which is not specifically limited herein.
The detection component, upon receiving a detection task for a first page of any of the plurality of pages of applet a1, may open the first page in client B of the paymate and inject a detection code in the first page. Thereafter, the detection component can perform private data disclosure detection on the first page using the detection code. If the first page is detected to have the private data leaked, a detection result may be generated and returned, and the detection result may be used to indicate that the first page has the private data leaked.
The following describes specific implementation steps of the above method with reference to specific examples.
Referring to fig. 2, a schematic diagram of one embodiment of a method for private data disclosure detection for an applet is shown. The small program is borne by the service platform, and the detection assembly and the client of the service platform are located in the same terminal device. The method comprises the following steps:
step 202, the detection server side obtains a plurality of pages of the small program according to the program identification of the small program;
step 204, the detection server generates a detection task list aiming at the applet, wherein each detection task comprises different pages in the multiple pages;
step 206, the detection server side issues each detection task to the detection component in sequence;
step 208, in response to receiving a detection task for any first page of the multiple pages, the detection component opens the first page in the client of the service platform, and injects a detection code into the first page, where the detection code includes the first code;
step 212, the detection component searches a first type of triggerable control in a first page by using a first code, wherein the first type of triggerable control is used for user trigger privacy data authorization of the client;
step 214, if the first type of triggerable control is found, the detection component executes a first trigger event of the first type of triggerable control in the first page;
step 216, the detection component acquires first information returned by a background server of the applet aiming at the first trigger event, and a first interface used by the background server for transmitting the first information;
in step 218, the detection component determines whether the first information includes plaintext privacy data;
if the determination result is yes, the detection component generates and returns a first detection result, wherein the first detection result includes the first interface and is used for indicating that the first interface has the private data leaked.
The above steps are further explained below.
In step 202, the detection server may obtain a plurality of pages of the applet from the service platform according to the program identifier of the applet. Wherein the plurality of pages may be part or all of the pages of the applet. Note that the page of the applet is typically an HTML5 page. Further, the service platform comprises a service end, and the detection service end can acquire a plurality of pages of the applet from the service end of the service platform according to the program identifier of the applet.
Optionally, the multiple pages of the applet and the program identifier of the applet may be stored in the database of the service platform in advance, and the detection server may obtain the multiple pages from the database according to the program identifier of the applet.
It should be understood that the present specification does not specifically limit the method of acquiring the multiple pages of the applet.
Next, in step 204, the detection server may generate a detection task list for the applet according to a plurality of pages of the applet. Each detection task in the detection task list includes a different page of the plurality of pages.
Next, in step 206, the detection server may issue each detection task in the detection task list to the detection component in sequence. Specifically, the detection server may issue each detection task to the detection component at one time, or the detection server may issue one detection task of each detection task each time, which is not specifically limited herein.
In practice, the detection server may issue the detection task using the lua script. lua is a small script language, the code is simple and graceful, and the lua can be compiled and run on almost all operating systems and platforms.
In the case of issuing one detection task at a time, the detection server may execute a task issuing process 300 as shown in fig. 3. The task issuing process 300 includes the following steps:
The detection result returned by the detection task can be used for indicating that private data of the page included in the detection task is leaked. Specifically, the detection result may be, for example, the first detection result generated in step 220, or the second detection result mentioned hereinafter.
In general, for any detection task in the detection task list, after the detection component completes detection on a page included in the detection task, if the private data is leaked from the page, a detection result indicating that the private data is leaked may be returned to the detection server, and then the detection server may issue a next detection task of the detection task in response to receiving the detection result. If the page has no private data leakage, a detection completion notification message can be returned to the detection server, and then the detection server can respond to the reception of the detection completion notification message and issue the next detection task of the detection task.
Optionally, after the detection component completes detection on the page included in the detection task, no matter whether the page has the private data leaked, the detection component may return a detection completion notification message to the detection server, and the detection server may issue a next detection task of the detection task in response to receiving the detection completion notification message.
With continued reference to the corresponding embodiment of fig. 2, in step 208, the detection component may open a first page in the client of the service platform and inject detection code in the first page in response to receiving a detection task for the first page of any of the plurality of pages.
The detection code includes, but is not limited to, a first code for detecting a first type of triggerable control in a page. A first type of triggerable control is for a user of a client to trigger privacy data authorization. The private data may be any private data of the user saved to the service platform, and may include, for example, a login password of a registered account of the user, a key of the registered account, an identification number, a bank card number, a phone book, a short message record, a call record and/or a photo, and so on.
In some embodiments, the first type of triggerable control may be a button control. The button control may be a plain text button (e.g., the grant privacy authorization button indicated by reference numeral 401 in fig. 4 a), a text box button (e.g., the grant privacy authorization button indicated by reference numeral 402 in fig. 4 b), or a plain picture button, etc., which is not limited in this regard.
In practice, the application framework employed by the client of the service platform includes an applet container for loading pages of an applet. Based on this, the detection component can inject detection code into the applet container of the client, such that the applet container loads the detection code while loading the first page, thereby causing the detection code to be injected into the first page.
It should be noted that the detection component may obtain the operation handle of the first page, and operate the first page according to the operation handle.
The detection component, after injecting the detection code into the first page, can then perform step 212 to search the first page for a first type of triggerable control using the first code.
In some embodiments, the detection code may further include second code for finding a page element in the page. Wherein a page element is a basic unit for building a page. For any page, it may include page elements such as text entry boxes, button controls, drop-down boxes, list boxes, scroll bars, page turn controls, Tab controls, hyperlinks, upload controls, and/or download controls.
To facilitate finding the first type of triggerable control using the first code, step 210 may also be performed to find a plurality of page elements from the first page using the second code, prior to step 212. Based on this, in step 212, a first type of triggerable control may be looked up in the plurality of page elements using a first code. The plurality of page elements may be part or all of the page elements of the first page. Further, the plurality of page elements may be respective triggerable (e.g., clickable) page elements in the first page.
Specifically, in step 210, the detection component may obtain, by using the second code, handles of the multiple page elements from a local framework (which may also be referred to as a Native layer) of the terminal device where the detection component is located, so that in step 212, the first type triggerable control may be searched for in the multiple page elements according to the handles by using the first code.
In some embodiments, the first code may contain conditions and/or rules for finding a first type of triggerable control. The conditions and the rules may be designed empirically by the skilled person and are not specifically limited herein.
In some embodiments, a complete library of functions may be custom packaged in advance, which may include a first function for the first code to call. The first function is used to find a first type of triggerable control. It is to be noted that the function library may include one or more first functions, and is not particularly limited herein.
Based on this, the detection code may also include a code of the function library. In step 212, a first function may be called with a first code to find a first type of triggerable control in a first page. Further, a first function may be called with the first code to find a first type of triggerable control among the plurality of page elements. Further, a first function may be called by using the first code, so as to search the first type of triggerable control in the plurality of page elements according to the handles of the plurality of page elements.
If the first type of triggerable control is found in the first page, the detection component may perform step 214 to perform a first triggering event for the first type of triggerable control in the first page. The first trigger event may be, for example, a click event or a touch event, and is not limited in this respect. Taking the terminal device as a smartphone as an example, in the case where the smartphone presents a first page as shown in fig. 4a or fig. 4b, the detection component may perform a click event agreeing to the privacy authorization button.
After step 214, the applet typically sends a notification message to its backend server that the user agrees to privacy authorization in response to the first trigger event. And then, the background server side acquires the privacy data of the user from the service platform according to the notification message. Then, the background server will perform message feedback on the applet. Here, for convenience of description, a message that the background server feeds back to the applet for the first trigger event is referred to as first information, and an interface that the background server uses to transmit the message is referred to as a first interface. Based on this, after step 214, the detection component can capture the first interface and the first information by performing step 216.
Next, in step 218, the detection component may determine whether the first information includes plaintext privacy data. Wherein the plaintext privacy data is privacy data without desensitization.
Generally, some plaintext privacy data, such as identification numbers, bank card numbers, etc., employ a specific encoding rule, and a technician may design a detection policy for the plaintext privacy data in advance according to the encoding rule, and write the detection policy into the detection component. Based thereon, in step 218, the detection component can determine whether the first information includes clear privacy data based on locally stored personal privacy data of the user and/or a detection policy.
If the determination of the detection component in step 218 is yes, the detection component can then execute step 220 to generate and return a first detection result, which includes the first interface, and is used to indicate that the first interface has private data leaked.
The method for detecting the leakage of the private data for the applet, provided by the embodiment corresponding to fig. 2, may enable the detection component to perform the detection of the leakage of the private data on the first page in a code injection manner. By adopting the detection scheme, the private data leakage detection of various applets borne by the service platform can be realized. In addition, automatic dynamic inspection of each page of the applet can be realized, and the detection accuracy and the detection efficiency can be greatly improved.
In some embodiments, the detection code may further include a third code. The third code may be used to look up a second type of triggerable control in the page and/or clear text privacy data presented on the page. Wherein the second type of triggerable control is a triggerable control other than the first type of triggerable control. Further, the second type of triggerable control may belong to a preset control category. The preset control category may be a control category that is set empirically by a technician and may be related to leakage of private data. The preset control category may include, for example, a button control, an upload control, a download control, and/or a hyperlink, etc., and is not particularly limited herein.
It should be noted that the third code and the first code in the foregoing may be the same code or different codes, and are not limited in this respect.
If the first type of triggerable control is not located in the first page in step 212, it may be indicated that the first page is a page subsequent to the user's authorized private data, in which case the applet may store some private data authorized by the user. In addition, the first page may present private data that the applet loads from the local and/or private data that is obtained from the backend server. In addition, a triggerable control for triggering the acquisition of the private data from the local or background server side may be included in the first page. Obviously, the page presented after the user authorizes the private data also has the problem of leakage of the private data.
In order to realize comprehensive detection of the leakage of the private data and further improve the security of the private data of the user, under the condition that the first type of triggerable control is not searched from the first page, the detection component can search the second type of triggerable control and/or the plaintext private data in the first page by using the third code, so that whether the private data are leaked from the first page is determined according to the search result. In particular, the detection component can utilize a third code to find a second type of triggerable control among the plurality of page elements as previously described.
Optionally, the function library as described above may further include a second function and/or a third function. The second function is used to find a second type of triggerable control. The third function is used to find the clear privacy data presented on the page. The number of the second function and the third function may be one or more, and is not limited in particular.
Based on this, to facilitate finding the first type of triggerable control and/or the plaintext privacy data using the third code, the second function may be invoked using the third code to find the second type of triggerable control in the first page, and/or the third function may be invoked using the third code to find the plaintext privacy data in the first page. In particular, a second function may be called with a third code to find a second type of triggerable control in the plurality of page elements as previously described.
It should be noted that, by injecting a function library into a page and calling a function in the function library to search for a target object in the page (e.g., a first type triggerable control, a second type triggerable control, and plaintext privacy data), not only can search efficiency be improved, but also a technician can conveniently and quickly optimize a detection code when a detection requirement changes, for example, only the logic of the first code and/or the third code in the foregoing needs to be optimized.
Next, taking an example that the third code is used for searching the second type of triggerable control and the plaintext privacy data in the page, the method for detecting disclosure of the privacy data for the applet will be described.
Specifically, if the detection component does not find the first type of triggerable control in step 212, then process 500 shown in fig. 5 may be performed. FIG. 5 is a flow diagram of one embodiment of a method for private data disclosure detection for an applet. The process 500 includes the following steps:
in step 504, for each found second type triggerable control, the following steps 5042 and 5048 are performed:
if the determination result is yes, step 5048, classify one of the following items into the second detection result: the second interface is used for transmitting second information by the second type of triggerable control and the background server of the applet;
and step 508, returning a second detection result.
The steps shown in fig. 5 will be further explained below.
In step 502, the search for the second type triggerable control and the plaintext privacy data in the first page may be performed serially or in parallel. During serial execution, the second type of triggerable control in the first page may be searched first, and then the plaintext privacy data in the first page may be searched, or the plaintext privacy data in the first page may be searched first, and then the second type of triggerable control in the first page may be searched, which is not limited specifically herein.
Additionally, the library of functions as previously described may include a second function and a third function. The detection component can invoke a second function with a third code to find a second type of triggerable control in the first page and invoke a third function with the third code to find the plaintext privacy data in the first page.
If the second type of triggerable control is found by performing step 502, then step 504 may be performed. If the plaintext privacy data is found by performing step 502, step 506 may be performed.
In step 504, for each second type of triggerable control found, such as the view personal real name information button pointed to by reference numeral 601 in the "my" page shown in FIG. 6a, step 5042 and 5048 may be performed.
Specifically, in step 5042, a second triggering event, such as a click event, for viewing the personal real name information button may be performed in the My page. The applet may then obtain second information, such as the user's personal real name information, which typically includes the user's real name and identification number, from the local or backend server in response to the click event. Based on this, the detection component may perform step 5044, capturing the personal real name information that the applet obtained in response to the click event. Next, the detection component can perform step 5046 to determine whether the personal real-name information includes plaintext privacy data. For example, if the detection component detects that the identification number in the personal real-name information is not desensitized, it may be determined that the personal real-name information includes plaintext privacy data, and then step 5048 may be executed to attribute one of the following to the second detection result: and the identifier of the button for viewing the personal real-name information and an interface (namely a second interface) used by the background server of the applet for transmitting the personal real-name information are checked.
It should be noted that, if the personal real-name information is obtained locally by the applet, the identifier of the button for viewing the personal real-name information may be included in the second detection result, and the second detection result may be used to indicate that the button for viewing the personal real-name information has the privacy data leaked. If the personal real-name information is acquired from the background server by the applet, an interface used by the background server for transmitting the personal real-name information can be classified into a second detection result, and the second detection result can be used for indicating that privacy data are leaked from the interface.
In some embodiments, after performing step 5042, the detecting component may further block the applet from calling the information presentation interface, so as to avoid page jump, so that the detecting component detects the searched second-type triggerable controls respectively.
In step 506, for the found plain text privacy data, for example, the identification number "111111111111111111" without desensitization processing pointed by reference numeral 602 in the "personal center" page shown in fig. 6a, the search result information related to the identification number may be classified as the second detection result.
The search result information may include one of: the element identifier of the page element of the identity card number in the first page, and a background server of the applet are used for providing an interface (namely a third interface) of the identity card number. Specifically, if the identification number is locally loaded by the applet, the element identifier of the page element to which the identification number belongs in the first page may be included in the second detection result, and the second detection result may be used to indicate that the page element has the private data leaked. If the identification number is obtained by calling the interface by the applet, the interface can be classified into a second detection result, and the second detection result can be used for indicating that the interface has the privacy data leakage.
After performing steps 504 and 506, the detection component can perform step 508 and return the second detection result to the detection server.
In some embodiments, after the detection component completes the detection of the first page, a detection completion notification message may be returned to the detection server, so that the detection server learns that the detection component has completed the detection of the first page included in the current detection task according to the notification message, and then issues a next detection task of the current detection task to the detection component.
Generally, after receiving a first detection result or a second detection result corresponding to a first page, a detection server can not only know that private data is leaked from the first page according to the received detection result, but also know that a detection component has completed detection on the first page. Based on this, for the first page, the detection component may return a detection completion notification message to the detection server only in a case where no leakage of the private data is detected.
Wherein, if any one of the following is satisfied, it may indicate that the detection component has completed detecting the first page, and it is not detected that the first page has the private data leaked:
the result of the determination in step 218 is no;
the second type of triggerable control and the plaintext privacy data are not found in the step 502;
the plaintext privacy data is not found in step 502 above, and it is determined in step 504 above that each piece of the acquired second information does not include plaintext privacy data.
Further reference is made to fig. 7, which is a schematic structural diagram of a system for private data disclosure detection for applets. The system comprises a detection assembly and a detection server. The applet is borne by the service platform, and the detection component and the client of the service platform are located in the same terminal device.
The detection server is configured to obtain a plurality of pages of the applet according to the program identifier of the applet; generating a detection task list aiming at the small program, wherein each detection task comprises different pages in the multiple pages; and sequentially issuing each detection task to the detection component.
A detection component configured to respond to receiving a detection task aiming at any first page in the plurality of pages, open the first page in a client of the service platform and inject detection codes into the first page, wherein the detection tasks comprise the first codes; searching a first type of triggerable control in a first page by using a first code, wherein the first type of triggerable control is used for triggering privacy data authorization of a user of the client; if the first type of triggerable control is found, executing a first trigger event of the first type of triggerable control in a first page; acquiring first information returned by a background server of the applet aiming at a first trigger event, and a first interface used by the background server for transmitting the first information; determining whether the first information includes plaintext privacy data; if the determination result is yes, generating and returning a first detection result, wherein the first detection result comprises the first interface and is used for indicating that the first interface has the privacy data leakage.
Here, for further explanation of the detection server and the detection component, reference may be made to the related description in the foregoing, and details are not repeated here.
With further reference to fig. 8, the present specification provides one embodiment of an apparatus for private data disclosure detection for applets, which may be applied to a detection component (such as the detection component shown in fig. 1) on a terminal device. The applet is borne by the service platform, and the terminal device is provided with a client of the service platform.
As shown in fig. 8, the apparatus 800 for detecting leakage of privacy data for an applet of the present embodiment includes: a code injection unit 801, a lookup unit 802, an event trigger unit 803, an acquisition unit 804, a determination unit 805, and a generation unit 806. The code injection unit 801 is configured to open a first page in a client of a service platform and inject detection codes including the first code into the first page in response to receiving a detection task for the first page in the applet issued by a detection server; the search unit 802 is configured to search a first type of triggerable control in a first page using a first code, the first type of triggerable control being used for user-triggered privacy data authorization of a client; the event triggering unit 803 is configured to execute a first triggering event of the first type of triggerable control in the first page if the searching unit 802 finds the first type of triggerable control; the obtaining unit 804 is configured to obtain first information returned by a background server of the applet for the first trigger event, and a first interface used by the background server to transmit the first information; the determination unit 805 is configured to determine whether the first information includes plaintext privacy data; the generating unit 806 is configured to generate and return a first detection result including the first interface if the determination result of the determining unit 805 is yes, and is used for indicating that the first interface has the private data leaked.
In some embodiments, the code injection unit 801 may be further configured to: and injecting detection codes into the applet container of the client, so that the detection codes are injected into the first page.
In some embodiments, the code for detecting may further include code for a function library, the function library including a first function for finding a first type of triggerable control; and the lookup unit 802 may be further configured to: a first function is called by the first code to search a first type of triggerable control in a first page.
In some embodiments, the detection code further comprises a second code; and the lookup unit 802 may include: a first search subunit (not shown in the figure) configured to search for a plurality of page elements in the first page using the second code; a second finding subunit (not shown in the figure) configured to find the first type of triggerable control in the plurality of page elements using the first code.
In some embodiments, the detection code further comprises a third code; and the lookup unit 802 may further include: a third searching subunit (not shown in the figure) configured to search the first page for the second type of triggerable control by using a third code if the first type of triggerable control is not found in the first page; for each found second type of triggerable control, the event triggering unit 803 may be further configured to execute a second triggering event of the second type of triggerable control in the first page; the obtaining unit 804 may be further configured to obtain second information obtained by the applet in response to a second trigger event; the determination unit 805 may also be configured to determine whether the second information includes plaintext privacy data; the generating unit 806 may be further configured to, if the determining unit 805 determines that the second information comprises plaintext privacy data, attribute one of the following to the second detection result: the second interface is used for transmitting second information by the background server side and the identifier of the second type of triggerable control; the generating unit 806 may also be configured to return a second detection result.
In some embodiments, the generating unit 806 may be further configured to: if the second information is obtained locally by the applet, the identifier of the second type of triggerable control is classified into a second detection result; and if the second information is acquired by the applet from the background server, the second interface is classified into a second detection result.
In some embodiments, the apparatus 800 may further include: and the blocking unit (not shown in the figure) blocks the calling of the applet to the information display interface after the event triggering unit 803 executes a second triggering event of the second type of triggerable control in the first page.
In some embodiments, the third lookup subunit may be further configured to: searching plaintext privacy data in the first page by using the third code; the generating unit 806 may be further configured to: if the plaintext privacy data is found by the third searching subunit, the search result information is classified into the second detection result, and the search result information includes one of the following items: the element identifier of the page element of the found plaintext privacy data in the first page, and the third interface of the background server for providing the found plaintext privacy data.
In some embodiments, the code to detect further includes code to detect a library of functions, the library of functions including a second function to find a second type of triggerable control, and/or a third function to find plaintext privacy data for presentation on the page; and when the function library comprises the second function, the third search subunit may be further configured to: calling a second function by using a third code to search a second type of triggerable control in the first page; when the function library includes a third function, the third search subunit may be further configured to: a third function is invoked with the third code to look up the plaintext privacy data in the first page.
In some embodiments, the apparatus may further include: and a notification unit (not shown in the figure) for returning a detection completion notification message after the detection of the first page is completed.
In some embodiments, the detection task is included in a detection task list generated by the detection server for the applet, each detection task in the detection task list includes different pages in the multiple pages of the applet, and each detection task is sequentially issued to the detection component by the detection server.
In some embodiments, the detection task is issued by the detection server using the lua script.
In this embodiment, reference may be made to the related description above for specific processing of each unit and the technical effect brought by the processing of each unit, and details are not described herein again.
The present specification also provides a computer-readable storage medium, on which a computer program is stored, wherein when the computer program is executed in a computer, the computer program causes the computer to execute the method for detecting leakage of private data for an applet, which is respectively described in the above method embodiments.
The embodiment of the present specification further provides a computing device, which includes a memory and a processor, where the memory stores executable code, and when the processor executes the executable code, the method for detecting leakage of private data for an applet, which is described in each of the above method embodiments, is implemented.
The present specification also provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the method for detecting leakage of privacy data for an applet, which is described in the above method embodiments respectively.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in the embodiments disclosed herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The above-mentioned embodiments, objects, technical solutions and advantages of the embodiments disclosed in the present specification are further described in detail, it should be understood that the above-mentioned embodiments are only specific embodiments of the embodiments disclosed in the present specification, and are not intended to limit the scope of the embodiments disclosed in the present specification, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the embodiments disclosed in the present specification should be included in the scope of the embodiments disclosed in the present specification.
Claims (16)
1. A method for detecting privacy data leakage aiming at an applet is applied to a detection component on a terminal device, the applet is borne by a service platform, the terminal device is provided with a client of the service platform, and the method comprises the following steps:
in response to receiving a detection task for a first page in an applet, which is issued by a detection server, opening the first page in the client, and injecting a detection code into the first page, wherein the detection code comprises a first code;
searching a first type of triggerable control in the first page by using the first code, wherein the first type of triggerable control is used for triggering privacy data authorization by a user of the client;
if the first type of triggerable control is found, executing a first trigger event of the first type of triggerable control in the first page;
acquiring first information returned by a background server of the applet aiming at the first trigger event, and a first interface used by the background server for transmitting the first information;
determining whether the first information includes plaintext privacy data;
and if the determination result is yes, generating and returning a first detection result, wherein the first detection result comprises the first interface and is used for indicating that the first interface has private data leakage.
2. The method of claim 1, wherein said injecting detection code in the first page comprises:
injecting the detection code in an applet container of the client, thereby causing the detection code to be injected into the first page.
3. The method of claim 1, wherein the detection code further comprises code for a function library comprising a first function for finding the first type of triggerable control; and
the searching for the first type of triggerable control in the first page by using the first code includes:
calling the first function by using the first code to search the first page for the first type of triggerable control.
4. The method of claim 1, wherein the detection code further comprises a second code; and
the method further comprises the following steps:
searching a plurality of page elements in the first page by using the second code;
the searching for the first type of triggerable control in the first page by using the first code includes:
searching the first type of triggerable control in the plurality of page elements using the first code.
5. The method of claim 1, wherein the detection code further comprises a third code; and
the method further comprises the following steps:
if the first type of triggerable control is not found in the first page, searching a second type of triggerable control in the first page by using the third code;
for each found second type of triggerable control, executing a second trigger event of the second type of triggerable control in the first page; obtaining second information obtained by the applet in response to the second trigger event; determining whether the second information includes plaintext privacy data; if the determination result is yes, one of the following items is classified into the second detection result: the mark of the second type of triggerable control and a second interface of the background server for transmitting the second information are arranged;
and returning the second detection result.
6. The method according to claim 5, wherein the attributing one of the following to the second detection result specifically comprises:
if the second information is obtained locally by the applet, the identifier of the second type of triggerable control is classified into the second detection result;
and if the second information is acquired by the applet from the background server, classifying the second interface into the second detection result.
7. The method of claim 5, wherein after executing the second trigger event for the second type of triggerable control in the first page, further comprising:
and blocking the calling of the small program to the information display interface of the small program.
8. The method of claim 5, wherein prior to said returning said second detection result, further comprising:
searching plaintext privacy data in the first page by using the third code;
if the second detection result is found, the search result information is classified into the second detection result, and the search result information comprises one of the following items: the element identifier of the page element of the found plaintext privacy data in the first page, and the third interface of the background server for providing the found plaintext privacy data.
9. The method of claim 8, wherein the detection code further comprises code for a library of functions, the library of functions comprising a second function for finding the second type of triggerable control, and/or a third function for finding clear text privacy data presented on a page; and
when the function library comprises the second function, the searching for a second type of triggerable control in the first page by using the third code comprises:
calling the second function by utilizing the third code to search the second type of triggerable control in the first page;
when the function library includes the third function, the searching for plaintext privacy data in the first page using the third code includes:
and calling the third function by utilizing the third code to search plain text privacy data in the first page.
10. The method according to one of claims 1-9, further comprising:
and after the detection of the first page is finished, returning a detection completion notification message.
11. The method according to claim 1, wherein the detection tasks are included in a detection task list generated by the detection server for the applet, each detection task in the detection task list includes a different page of a plurality of pages of the applet, and each detection task is issued in sequence by the detection server to the detection component.
12. The method of claim 1, wherein the detection task is issued by the detection server using a lua script.
13. A system for private data leakage detection aiming at an applet comprises a detection server and a detection component, wherein the applet is borne by a service platform, and the detection component and a client of the service platform are positioned in the same terminal device;
the detection server is configured to acquire a plurality of pages of the applet according to the program identifier of the applet; generating a detection task list aiming at the small program, wherein each detection task comprises different pages in the multiple pages; sequentially issuing the detection tasks to the detection assembly;
the detection component is configured to respond to receiving a detection task aiming at a first page in any page of the plurality of pages, open the first page in the client and inject detection codes into the first page, wherein the detection codes comprise first codes; searching a first type of triggerable control in the first page by using the first code, wherein the first type of triggerable control is used for triggering privacy data authorization by a user of the client; if the first type of triggerable control is found, executing a first trigger event of the first type of triggerable control in the first page; acquiring first information returned by a background server of the applet aiming at the first trigger event, and a first interface used by the background server for transmitting the first information; determining whether the first information includes plaintext privacy data; and if the determination result is yes, generating and returning a first detection result, wherein the first detection result comprises the first interface and is used for indicating that the first interface has private data leakage.
14. An apparatus for detecting privacy data leakage for an applet, applied to a detection component on a terminal device, where the applet is borne by a service platform, and a client of the service platform is installed on the terminal device, the apparatus includes:
the code injection unit is configured to respond to the receiving of a detection task which is issued by a detection server and aims at a first page in an applet, open the first page in the client and inject detection codes into the first page, wherein the detection task comprises first codes;
a search unit configured to search the first page for a first type of triggerable control for a user of the client to trigger privacy data authorization using the first code;
the event triggering unit is configured to execute a first triggering event of the first type of triggerable control in the first page if the searching unit finds the first type of triggerable control;
the acquisition unit is configured to acquire first information returned by a background server of the applet aiming at the first trigger event, and a first interface used by the background server for transmitting the first information;
a determination unit configured to determine whether the first information includes plaintext privacy data;
and the generating unit is configured to generate and return a first detection result if the determination result of the determining unit is yes, wherein the first detection result comprises the first interface, and is used for indicating that the first interface has private data leakage.
15. A computer-readable storage medium, on which a computer program is stored, wherein the computer program causes a computer to carry out the method of any one of claims 1-12 when the computer program is carried out in the computer.
16. A computing device comprising a memory and a processor, wherein the memory has stored therein executable code that when executed by the processor implements the method of any of claims 1-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110699084.2A CN113326539B (en) | 2021-06-23 | 2021-06-23 | Method, device and system for private data leakage detection aiming at applet |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110699084.2A CN113326539B (en) | 2021-06-23 | 2021-06-23 | Method, device and system for private data leakage detection aiming at applet |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113326539A CN113326539A (en) | 2021-08-31 |
| CN113326539B true CN113326539B (en) | 2022-05-17 |
Family
ID=77424328
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110699084.2A Active CN113326539B (en) | 2021-06-23 | 2021-06-23 | Method, device and system for private data leakage detection aiming at applet |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113326539B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113986735A (en) * | 2021-10-28 | 2022-01-28 | 支付宝(杭州)信息技术有限公司 | Privacy risk detection method and device for target application |
| CN114880673B (en) * | 2022-04-28 | 2024-06-07 | 上海交通大学 | Method and system for detecting privacy data leakage aiming at applet source code |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104992113A (en) * | 2015-05-29 | 2015-10-21 | 北京奇虎科技有限公司 | Method and device for detecting whether privacy content of website is exposed, and cloud monitoring system |
| CN107133519A (en) * | 2017-05-15 | 2017-09-05 | 华中科技大学 | Privacy compromise detection method and system in a kind of Android application network communication |
| CN108509792A (en) * | 2017-02-23 | 2018-09-07 | 腾讯科技（深圳）有限公司 | A kind of injection loophole detection method and device |
| CN108647517A (en) * | 2018-05-17 | 2018-10-12 | 华中科技大学 | A kind of leakage location and method of the injection of Android mixing application code |
| CN110187931A (en) * | 2019-05-17 | 2019-08-30 | 北京百度网讯科技有限公司 | The operation method and device of small routine |
| CN111291374A (en) * | 2020-02-20 | 2020-06-16 | 支付宝(杭州)信息技术有限公司 | Application program detection method, device and equipment |
| CN111382424A (en) * | 2018-12-27 | 2020-07-07 | 全球能源互联网研究院有限公司 | Mobile application sensitive behavior detection method and system based on controlled environment |
| CN111400722A (en) * | 2020-03-25 | 2020-07-10 | 深圳市腾讯网域计算机网络有限公司 | Method, apparatus, computer device and storage medium for scanning small program |
| CN111475246A (en) * | 2020-04-10 | 2020-07-31 | 腾讯科技（深圳）有限公司 | Applet page display method, device, terminal and storage medium |
| CN111563260A (en) * | 2020-03-27 | 2020-08-21 | 中南大学 | Android application program-oriented Web injection code execution vulnerability detection method and system |
| CN112560090A (en) * | 2020-12-15 | 2021-03-26 | 建信金融科技有限责任公司 | Data detection method and device |
| CN112860566A (en) * | 2021-03-02 | 2021-05-28 | 百度在线网络技术（北京）有限公司 | Applet detection method, device, electronic equipment and readable medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2015258733B2 (en) * | 2014-05-14 | 2020-03-12 | Pagecloud Inc. | Methods and systems for web content generation |
| US10719611B2 (en) * | 2017-09-27 | 2020-07-21 | Servicenow, Inc. | Static security scanner for applications in a remote network management platform |
-
2021
- 2021-06-23 CN CN202110699084.2A patent/CN113326539B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104992113A (en) * | 2015-05-29 | 2015-10-21 | 北京奇虎科技有限公司 | Method and device for detecting whether privacy content of website is exposed, and cloud monitoring system |
| CN108509792A (en) * | 2017-02-23 | 2018-09-07 | 腾讯科技（深圳）有限公司 | A kind of injection loophole detection method and device |
| CN107133519A (en) * | 2017-05-15 | 2017-09-05 | 华中科技大学 | Privacy compromise detection method and system in a kind of Android application network communication |
| CN108647517A (en) * | 2018-05-17 | 2018-10-12 | 华中科技大学 | A kind of leakage location and method of the injection of Android mixing application code |
| CN111382424A (en) * | 2018-12-27 | 2020-07-07 | 全球能源互联网研究院有限公司 | Mobile application sensitive behavior detection method and system based on controlled environment |
| CN110187931A (en) * | 2019-05-17 | 2019-08-30 | 北京百度网讯科技有限公司 | The operation method and device of small routine |
| CN111291374A (en) * | 2020-02-20 | 2020-06-16 | 支付宝(杭州)信息技术有限公司 | Application program detection method, device and equipment |
| CN111400722A (en) * | 2020-03-25 | 2020-07-10 | 深圳市腾讯网域计算机网络有限公司 | Method, apparatus, computer device and storage medium for scanning small program |
| CN111563260A (en) * | 2020-03-27 | 2020-08-21 | 中南大学 | Android application program-oriented Web injection code execution vulnerability detection method and system |
| CN111475246A (en) * | 2020-04-10 | 2020-07-31 | 腾讯科技（深圳）有限公司 | Applet page display method, device, terminal and storage medium |
| CN112560090A (en) * | 2020-12-15 | 2021-03-26 | 建信金融科技有限责任公司 | Data detection method and device |
| CN112860566A (en) * | 2021-03-02 | 2021-05-28 | 百度在线网络技术（北京）有限公司 | Applet detection method, device, electronic equipment and readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113326539A (en) | 2021-08-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109376078B (en) | Mobile application testing method, terminal equipment and medium | |
| US10547624B2 (en) | Identity authentication method, apparatus, and system | |
| US11762979B2 (en) | Management of login information affected by a data breach | |
| CN113326539B (en) | Method, device and system for private data leakage detection aiming at applet | |
| CN105591743B (en) | Method and device for identity authentication through equipment operation characteristics of user terminal | |
| EP3176719B1 (en) | Methods and devices for acquiring certification document | |
| CN109684873B (en) | Data access control method and device, computer equipment and storage medium | |
| CN108256322B (en) | Security testing method and device, computer equipment and storage medium | |
| CN112394864B (en) | Information acquisition method and device, computer equipment and storage medium | |
| US20180167379A1 (en) | Method and device for processing user operation | |
| CN109547426B (en) | Service response method and server | |
| CN108418797B (en) | Webpage access method and device, computer equipment and storage medium | |
| WO2021244531A1 (en) | Payment method and apparatus based on facial recognition | |
| CN111866885A (en) | Verification information sharing method and device and electronic equipment | |
| US11809556B2 (en) | System and method for detecting a malicious file | |
| CN111669744B (en) | Information processing method and device and electronic equipment | |
| US20180174150A1 (en) | Systems and methods for processing a payment transaction authorization request | |
| US9720705B2 (en) | System and method of demand oriented user interface framework | |
| US20150149928A1 (en) | Method, system and device for implementing an instant messaging application | |
| CN112560815B (en) | File calling method, device, medium and electronic equipment | |
| CN112182561B (en) | Rear door detection method and device, electronic equipment and medium | |
| CN111259374B (en) | Authority abnormity detection method and device, computer equipment and storage medium | |
| CN111666567A (en) | Detection method, device, computer program and medium for malicious modification of application program | |
| CN111414525B (en) | Method, device, computer equipment and storage medium for acquiring data of applet | |
| WO2017129068A1 (en) | Event execution method and device and system therefor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40057022 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |