# US 2018/0343239 A1 · Hard coded credential bypassing

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0343239 A1
- Document ID: US20180343239A1
- Status: Published application
- Kind: A1
- Application number: 15/604,154
- Filed: 2017-05-24
- Published: 2018-11-29
- Earliest claimed: 2017-05-24
- Assignees: Micro Focus Software Inc.
- Applicants: Micro Focus Software Inc.
- Inventors: Gulshan Govind Vaswani
- Web page: https://patentgrep.com/patent/US20180343239A1

## CPC

- G06F 9/543: {User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]}
- H04L 63/0815: {providing single-sign-on or federations}
- H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

An existing application processing on a client device initiates a function to provide a hard coded credential to a remote target application for purposes of logging into and gaining access to the remote target application. A hook to the function causes an agent to be activated, the agent dynamically contacts a credential vault to obtain a randomly generated credential for access to the remote target application. The hook injects the randomly generated credential over the hard coded credential supplied by the existing application and the function is initiated. The function logs into the target application using the randomly generated credential providing the existing application access to the remote target application. The hard coded credential is bypassed by the randomly generated credential.

## Claims

### Claim 1

A method, comprising;
bypassing an internal portion of processing for an existing application processing on a client;
obtaining a randomly generated credential on behalf of the existing application; and
injecting the randomly generated credential into the internal portion of the processing for allowing the existing application to log into a target application with the randomly generated credential.

### Claim 2 (depends on 1)

The method of claim 1, wherein bypassing further includes processing hook to jump to the method processing when the existing application calls the internal portion as a call to an internal function made by the existing application.

### Claim 3 (depends on 2)

The method of claim 2, wherein processing further includes processing the hook as a trampoline function that processes as a first instruction of the internal function.

### Claim 4 (depends on 2)

The method of claim 2, wherein processing further includes processing the hook as an Application Programming Interface (API) hook that is a dynamically linked library injected into a processing space within the existing application on the client.

### Claim 5 (depends on 1)

The method of claim 1, wherein obtaining further includes authenticating to a credential store and making a request for the randomly generated credential.

### Claim 6 (depends on 5)

The method of claim 5, wherein authenticating further includes obtaining processing information for the existing application from an Operating System (OS) that the existing application processes within on the client.

### Claim 7 (depends on 1)

The method of claim 1, wherein obtaining further includes passing the processing information to the credential store for authenticating the request.

### Claim 8 (depends on 1)

The method of claim 1, wherein injecting further includes writing over a hard coded credential with the randomly generated credential, wherein the hard coded credential provided as input to the internal portion by the existing application when the existing application called the internal portion.

### Claim 9 (depends on 8)

The method of claim 8, wherein writing further includes reporting to a credential store from which the randomly generated credential was obtained that the existing application has received the randomly generated credential.

### Claim 10 (depends on 1)

The method of claim 1 further comprising, processing the method without any coding modifications made to the existing application.

### Claim 11 (depends on 1)

The method of claim 1 further comprising, processing the method as an Operating System (OS) hooking Application Programming Interface (API) and an agent that process on the client.

### Claim 12

A method, comprising;
receiving a request for a credential from an agent processing on a client;
authenticating an existing application for the request based on processing information or the existing application provided by the agent; and
provide the credential to the agent for the agent to inject into the processing of the existing application on the client and log into a target application for authenticated access to the target application.

### Claim 13 (depends on 12)

The method of claim 12, wherein receiving further includes receiving the request based on the existing application attempting to internally process a function that logs into the target application with a hard coded credential provided by the existing application to the function.

### Claim 14 (depends on 12)

The method of claim 12, wherein authenticating further includes providing the processing information to a policy engine to authenticate the existing application for the request.

### Claim 15 (depends on 12)

The method of claim 12, wherein providing further includes maintaining the credential with an account that the existing application has with the target application.

### Claim 16 (depends on 15)

The method of claim 15, wherein maintaining further includes processing an Application Programming Interface (API) of the target application to randomly create and define the credential for the account through the target application in advance of receiving the request from the agent.

### Claim 17 (depends on 16)

The method of claim 16, wherein processing further includes processing the API to establish a new randomly generated credential that replaces the credential for the account in response to receiving an indication from the agent that the existing application has logged into the target application with the credential.

### Claim 18 (depends on 12)

The method of claim 12, wherein injecting further includes placing a lock on the credential when provided to the agent ensuring that the credential cannot be provided or used by a different existing application and different agent interfaced to the method.

### Claim 19

A system, comprising:
a client configured with an agent; and
a server configured with a credential manager;
wherein the agent is configured to: i) execute on at least one hardware processor of the client, ii) bypass an internal login process of an existing application when the existing application attempts to log into a target application with a hard coded credential, iii) interact with the credential manager to obtain a replacement credential, and iv) replace the hard coded credential with the replacement credential and process the internal login process of the existing application, and wherein the credential manager is configured to: a) execute on at least one hardware processor of the server, b) interact with the agent to authenticate the existing application for the replacement credential, c) provide the replacement credential to the agent, and d) manage an account that the existing application has with the target application to define the replacement credential and to change the replacement credential.

### Claim 20 (depends on 19)

The system of claim 19, wherein the credential manager is further configured, in b), to: interact with a policy engine to authenticate the existing application for the replacement credential based on processing information for the existing application provided by the agent.
